Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/reggiechan74/cc-plugins/update-marketplacegit clone --depth 1 https://github.com/reggiechan74/cc-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/reggiechan74/cc-plugins/update-marketplace)<a href="https://agentmods.dev/commands/reggiechan74/cc-plugins/update-marketplace"><img src="https://agentmods.dev/badge/commands/reggiechan74/cc-plugins/update-marketplace.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00010 | $0.00848 |
| Opus 5 | $0.00005 | $0.00424 |
| Sonnet 5 | $0.00002 | $0.00170 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
update-marketplace scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Marketplace
Scan the repository for plugins and update both the marketplace registry and documentation.
Arguments received: $ARGUMENTS
Instructions
Step 1: Scan for Plugins
Scan the root directory /workspaces/claude-plugins/ for plugin directories. A valid plugin is identified by:
- Modern format: A directory containing
.claude-plugin/plugin.json - Legacy format: A directory containing
manifest.jsonat root level
Exclude these directories:
.git.claude-plugin(the root marketplace config).claude(commands/skills directory)node_modules- Any hidden directories (starting with
.)
For each plugin found, extract:
name: From plugin.json or manifest.jsonversion: From plugin.json or manifest.jsondescription: From plugin.json or manifest.jsonsource: Relative path from root (e.g.,./spinnerverbs-plugin)
Step 2: Read Current State
Read the current marketplace.json from /workspaces/claude-plugins/.claude-plugin/marketplace.json.
Compare discovered plugins against existing entries to identify:
- New plugins: Not in marketplace.json
- Updated plugins: Version or description changed
- Removed plugins: In marketplace.json but directory no longer exists
Step 3: Update marketplace.json
Update /workspaces/claude-plugins/.claude-plugin/marketplace.json with the complete list of discovered plugins.
Format:
{
"name": "cc-plugins",
"owner": {
"name": "Reggie Chan"
},
"plugins": [
{
"name": "plugin-name",
"source": "./plugin-directory",
"description": "Plugin description from manifest",
"version": "1.0.0"
}
]
}
Sort plugins alphabetically by name.
Step 4: Update README.md
Update /workspaces/claude-plugins/README.md to document all plugins.
For each plugin:
- Read its README.md to extract features and commands
- Look for
## Featuressection for feature list - Look for
## Commandsor## Usagesections for commands
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 158 lines · 10 tokens per session scan A 8c49591b8568
update-marketplace is a command published in the GitHub repository reggiechan74/cc-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 848 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.