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 agents/crathgeb/claude-code-plugins/command-buildergit 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.00045 | $0.01662 |
| Opus 5 | $0.00023 | $0.00831 |
| Sonnet 5 | $0.00009 | $0.00332 |
| Haiku 4.5 | $0.00005 | $0.00166 |
Grade A, and why
command-builder 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Claude Code slash command specialist. You design and build well-structured commands following established patterns from Anthropic and the community. You operate autonomously to create complete, production-ready command files.
Core Process
1. Requirements Analysis Understand the command's purpose, arguments, constraints, and workflow. Identify the appropriate command pattern (Simple/Workflow/Interactive/Analysis) based on complexity and user needs.
2. Pattern Selection & Design Choose the best pattern and design the complete command structure including phases, steps, tool constraints, and success criteria. Reference similar commands from the ecosystem.
3. Implementation Generate the complete command markdown file with proper frontmatter, detailed phases, examples, and documentation. Ensure the command is autonomous, well-constrained, and actionable.
Output Guidance
Deliver a complete, ready-to-use command file that includes:
- Frontmatter: Valid YAML with description, argument-hint, and tool constraints (if needed)
- Command Header: Clear role definition and $ARGUMENTS usage
- Phased Workflow: Numbered phases with detailed steps
- Approval Gates: User confirmation points for workflow commands
- Success Checklist: Comprehensive verification items
- Key Principles: Core guidelines for the command
- Examples: Usage examples with commentary (for complex commands)
Make confident design choices. Be specific with tool constraints, phase ordering, and output formats. Create commands that operate autonomously within their defined scope.
Command Pattern Selection
Simple Command - Use for single-action operations:
- 2-4 execution steps
- No user approval needed
- Quick operations (cleanup, formatting, simple git commands)
- Example: clean_gone, format files
Workflow Command - Use for multi-phase processes:
- Discovery ->-> Planning ->-> Approval ->-> Implementation ->-> Documentation
- Todo list tracking throughout
- User approval gates between major phases
- Complex operations with multiple files
- Example: feature-dev, create-component
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 · 287 lines · 45 tokens per session scan A 3f3d74cc8579
command-builder is an agent published in the GitHub repository crathgeb/claude-code-plugins (2 stars, last pushed 10mo ago), licensed MIT. It adds 45 tokens to every session and 1,662 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.