Index of every page on this site: llms.txt
All skills
am-will avatar

/pluginstaller

@9f954c3
by am.willam-will/codex-skills1k stars
60
Run it yourself

Add a Codex plugin from a GitHub repo to a repo or personal marketplace using the current Codex plugin layout and marketplace metadata.

Use this Skill: https://skilld.dev/gh/am-will/codex-skills/pluginstaller

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈38 tokens for metadata: the name and description. ≈1k when used: this file. ≈368 more on demand in 2 files.

Description uses 1.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈151 characters, or 1.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Pluginstaller

Use when the user gives a GitHub repo for a Codex plugin and wants it available in Codex.

Follow the current Codex plugin docs. Do not invent alternate install flows.

Inputs

  • GitHub repo URL or owner/repo
  • Install scope: repo or personal
  • If the repo contains more than one plugin root, ask which plugin folder to install.

Workflow

  1. If the user does not specify whether the plugin should be repo-scoped or personal, stop and ask.
  2. Fetch the repo and locate the plugin root by finding .codex-plugin/plugin.json.
  3. Read .codex-plugin/plugin.json and validate the canonical structure:
    • name, version, and description should exist.
    • Bundled paths such as skills, apps, and mcpServers should be relative to the plugin root and start with ./.
    • Only plugin.json should live inside .codex-plugin/.
  4. Prefer the built-in @plugin-creator skill when the task is to scaffold a new local plugin or add an existing local plugin to a marketplace. Use the manual path below when you are wiring up a repo the user already provided.
  5. Copy the entire plugin directory, not just SKILL.md, into a marketplace-visible location. Default to the documented standard locations unless the repo already uses a different valid marketplace-relative path:
    • repo: $CWD/plugins/<plugin-name> and $CWD/.agents/plugins/marketplace.json
    • personal: ~/.codex/plugins/<plugin-name> and ~/.agents/plugins/marketplace.json
  6. Preserve the full bundle at the plugin root, including sibling skills/, .app.json, .mcp.json, assets/, and any other plugin files. Do not move those files under .codex-plugin/.
  7. Create or update the marketplace file with the documented schema:
    • top-level marketplace name
    • optional interface.displayName
    • plugin entry name
    • source.source = "local"
    • source.path relative to the marketplace root:
      • repo: ./plugins/<plugin-name>
      • personal: ./.codex/plugins/<plugin-name>
    • policy.installation
    • policy.authentication
    • category
  8. Use marketplace values that match the docs unless the user says otherwise:
    • policy.installation = "AVAILABLE"
    • policy.authentication = "ON_INSTALL"
    • category from interface.category when present, otherwise Productivity
  9. Merge into any existing marketplace file instead of replacing it.
  10. Restart Codex and verify the plugin appears in /plugins.
  11. Report the runtime behavior accurately:
  • The marketplace entry points to the source plugin directory.
  • Codex installs the plugin into ~/.codex/plugins/cache/<marketplace>/<plugin>/<version>/.
  • For local plugins, the installed cache version is local.
  • Plugin enabled or disabled state is stored in ~/.codex/config.toml.

Rules

  • Prefer the terms repo marketplace and personal marketplace over workspace and global.
  • Do not present copying into plugins/ as the complete install. The marketplace entry is what makes the plugin discoverable in Codex.
  • Do not flatten or rename the plugin bundle.
  • Keep the plugin name stable and consistent across folder, manifest, and marketplace entry.
  • Keep manifest and marketplace paths relative and ./-prefixed where the docs require it.
  • Treat the documented repo and personal plugin directories as defaults, not absolute requirements, as long as the marketplace source.path remains valid and stays inside the marketplace root.
  • If the repo already ships a marketplace file, prefer it as the source of truth for marketplace ordering and metadata, and only add or update the plugin entry that is needed.
  • If the manifest is missing required basics or uses invalid root-relative paths, fix the plugin structure before claiming installation is complete.

Scope guide

Use repo when the plugin should live with one repo or be shared through that repo's marketplace. Use personal when the plugin should be available from the user's own Codex setup across projects.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill installs third-party plugins from GitHub repositories into local directories. While this is the intended functionality, it involves downloading untrusted content and writing to the user's home directory, which presents inherent risks if the source repository is malicious.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: MEDIUM · 1 issue

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 9f954c3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 8 months ago

README badge

README badge for am-will/codex-skills/pluginstaller