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 instructions/pigfoot/claude-code-hubs/claude-mdgit clone --depth 1 https://github.com/pigfoot/claude-code-hubsWrote 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/instructions/pigfoot/claude-code-hubs/claude-md)<a href="https://agentmods.dev/instructions/pigfoot/claude-code-hubs/claude-md"><img src="https://agentmods.dev/badge/instructions/pigfoot/claude-code-hubs/claude-md.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.00402 | $0.00402 |
| Opus 5 | $0.00201 | $0.00201 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
claude-code-hubs CLAUDE.md 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 5d 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.
What it actually says
Plugin Version Management
When updating plugin versions, ALWAYS update ALL of these locations:
For each plugin (e.g., nano-banana)
-
Plugin metadata (REQUIRED):
plugins/{plugin-name}/.claude-plugin/plugin.json-versionfield
-
Plugin documentation (REQUIRED):
plugins/{plugin-name}/README.md- Recent Improvements sectionplugins/{plugin-name}/skills/{skill-name}/SKILL.md- metadata version field
-
Marketplace version table (REQUIRED):
/README.md- "Available Plugins" table (line ~705)
Checklist Template
When bumping plugin version from X.Y.Z to X.Y.(Z+1):
# 1. Update plugin.json
plugins/{name}/.claude-plugin/plugin.json → version: "X.Y.(Z+1)"
# 2. Update README.md - Add new section at top
plugins/{name}/README.md → "## ✨ Recent Improvements (vX.Y.(Z+1))"
# 3. Update SKILL.md metadata
plugins/{name}/skills/{name}/SKILL.md → metadata.version: "X.Y.(Z+1)"
# 4. Update marketplace table
README.md → Available Plugins table → update version column
# 5. Verify no missed references
grep -r "X.Y.Z" plugins/{name}/ README.md
Common Mistakes to Avoid
- ❌ Updating plugin.json but forgetting marketplace table in root README.md
- ❌ Updating version number but not adding "Recent Improvements" section
- ❌ Forgetting to update SKILL.md metadata version
- ❌ Leaving old version numbers in documentation examples
Automation Idea (Future)
Consider adding a version bump script:
./scripts/bump-plugin-version.sh nano-banana 0.0.8
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.
- 5d ago First seen · 55 lines · 402 tokens per session scan A d85e2045b61f
claude-code-hubs CLAUDE.md is an instructions file published in the GitHub repository pigfoot/claude-code-hubs (5 stars, last pushed 1mo ago), licensed MIT. It adds 402 tokens to every session, about $0.0020 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 instructions, from other repositories
planning-with-files AGENTS.md
AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
OpenMicro AGENTS.md
Instructions for stephenleo/OpenMicro, covering openmicro — project conventions and releases.
ai-usagebar CLAUDE.md
Claude Code instructions for akitaonrails/ai-usagebar, covering claude.md, release checklist — must do all of these, hard invariants — never break these, secret-discipline rules (learned the hard way) and live api smoke discipline.
living-manual CLAUDE.md
Instructions for dougstanford/living-manual, covering living-manual, start of every session, how work lands — non-negotiable, user's manual (living-manual) and releasing.
yandex360-mcp CLAUDE.md
Claude Code instructions for pa1ch/yandex360-mcp, covering claude.md — гайд для ассистента, как устроен релиз (всё автоматически по тегу), процедура релиза (шаги ассистента), гарды and архитектура (кратко).