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-badgesgit clone --depth 1 https://github.com/reggiechan74/cc-pluginsWhat 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 | $0.00011 | $0.01367 |
| Opus 5 | $0.00005 | $0.00683 |
| Sonnet 5 | $0.00002 | $0.00273 |
| Haiku 4.5 | $0.00001 | $0.00137 |
Grade A, and why
update-badges 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 2d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Badges
Add or update shields.io badges on plugin README files.
Arguments received: $ARGUMENTS
Instructions
Step 1: Determine Targets
If $ARGUMENTS is provided, treat it as a plugin folder name (e.g., nano-banana-plugin). Validate that /workspaces/claude-plugins/$ARGUMENTS/.claude-plugin/plugin.json exists.
If $ARGUMENTS is empty, scan for all plugin directories by globbing */.claude-plugin/plugin.json under /workspaces/claude-plugins/. Exclude .git, .claude, .claude-plugin, node_modules, docs, and hidden directories.
Step 2: Auto-Detect Badges for Each Plugin
For each target plugin folder, read the following files to detect applicable badges:
- Read
.claude-plugin/plugin.json— extractname,version,license,repository,keywords - Read
README.md— note existing badges (lines containingimg.shields.io) - Read
LICENSE— if present, confirm license type from first line - Scan for language signals:
- Python files (
*.py) → Python badge package.json→ Node.js badge*.tsfiles → TypeScript badge*.shfiles only → Bash badge
- Python files (
- Scan skill files for API keywords:
- "Gemini" →
powered_by-Gemini_API-orange - "OpenAI" →
powered_by-OpenAI-412991 - "Google" (Calendar, Gmail, etc.) →
Google_Workspace-4285F4 - "ArcGIS" or "Esri" →
ArcGIS-2C7AC3
- "Gemini" →
- Always include: Claude Code plugin badge (
Claude_Code-plugin-blueviolet)
Build a candidate list of badges. Each badge has:
- label: Display name (e.g., "Version", "License: MIT")
- url: Full shields.io markdown (e.g.,
) - detected: Whether it was auto-detected (true) or an optional addition
Step 3: Present Badge Choices
Use AskUserQuestion with multiSelect: true to present the detected badges. Auto-detected badges should be listed first with "(Recommended)" in their label. Include these additional optional badges the user can opt into:
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.
- 2d ago First seen · 133 lines · 11 tokens per session scan A e73a8e91708d
update-badges is a command published in the GitHub repository reggiechan74/cc-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 1,367 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
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.