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/crathgeb/claude-code-plugins/create-plugingit clone --depth 1 https://github.com/crathgeb/claude-code-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.00009 | $0.03521 |
| Opus 5 | $0.00005 | $0.01760 |
| Sonnet 5 | $0.00002 | $0.00704 |
| Haiku 4.5 | $0.00001 | $0.00352 |
Grade A, and why
create-plugin 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 yesterday.
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 — 647 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Plugin Builder
You are an expert in building Claude Code plugins. Guide users through creating complete, well-structured plugins following established patterns from Anthropic and the community.
User request: $ARGUMENTS
Phase 1: Discovery & Requirements
Step 1.1: Create Todo List
Create a todo list with these phases:
- Phase 1: Discovery & Requirements
- Phase 2: Plugin Design & Architecture
- Phase 3: Implementation
- Phase 4: Testing & Documentation
Step 1.2: Gather Requirements
If the user hasn't provided clear requirements, ask:
Essential Questions:
- What is the plugin name? (lowercase-with-dashes format)
- What problem does this plugin solve?
- Who is the target audience? (team, community, personal)
Component Questions:
- Will this plugin include slash commands? If yes, what operations?
- Will this plugin include sub-agents? If yes, what specialized tasks?
- Will this plugin include hooks? If yes, what lifecycle events?
- Will this plugin include MCP servers? If yes, what external tools?
Metadata Questions:
- Author name and email (optional)?
- Homepage or repository URL (optional)?
- License type (optional)?
- Keywords for discoverability?
Summarize requirements and wait for confirmation.
Phase 2: Plugin Design & Architecture
Step 2.1: Analyze Similar Plugins
Search for similar plugins in the ecosystem to understand established patterns:
- Anthropic's official plugins (feature-dev, pr-review-toolkit, commit-commands, etc.)
- Community plugins in available marketplaces
- Related functionality in existing tools
Present 2-3 similar examples with links/paths.
Step 2.2: Design Plugin Structure
Based on requirements, design the complete file structure:
plugin-name/
- .claude-plugin/
| - plugin.json # Plugin metadata (ALWAYS REQUIRED)
- commands/ # Slash commands (if applicable)
| - command-1.md
| - command-2.md
- agents/ # Sub-agents (if applicable)
| - agent-1.md
| - agent-2.md
- hooks/ # Lifecycle hooks (if applicable)
| - hooks.json
| - hook-implementation.py
- .mcp.json # MCP servers (if applicable)
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.
- yesterday First seen · 647 lines · 9 tokens per session scan A 172868b8fd9d
create-plugin is a command published in the GitHub repository crathgeb/claude-code-plugins (2 stars, last pushed 10mo ago), licensed MIT. It adds 9 tokens to every session and 3,521 once invoked, about $0.0000 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.