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/madappgang/claude-code/helpgit clone --depth 1 https://github.com/MadAppGang/claude-codeWhat 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.00023 | $0.00777 |
| Opus 5 | $0.00012 | $0.00388 |
| Sonnet 5 | $0.00005 | $0.00155 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
agentdev-help 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Development Plugin Help
Present the following help information to the user:
Agent Development Plugin v1.1.0
Create, implement, and review Claude Code agents and commands with multi-model validation.
Quick Start
/agentdev:develop Design a GraphQL code reviewer agent
Agents (3)
| Agent | Description | Model |
|---|---|---|
| architect | Designs agent/command architecture, creates comprehensive design plans | Sonnet |
| developer | Implements agents/commands from approved design plans | Sonnet |
| reviewer | Reviews implemented agents for quality, completeness, standards compliance | Sonnet |
Commands (2)
| Command | Description |
|---|---|
| /agentdev:develop | Full-cycle agent development: design → plan review → implement → quality review |
| /help | Show this help |
/develop Workflow
- Design Phase - Architect creates comprehensive design plan
- Plan Review - Multi-model validation of architecture (Grok, Gemini, etc.)
- Implementation - Developer builds the agent from approved plan
- Quality Review - Reviewer validates against standards
Example
/agentdev:develop Create a database migration reviewer agent that checks SQL migrations for safety issues
Skills (3)
| Skill | Description |
|---|---|
| xml-standards | XML tag structure patterns following Anthropic best practices |
| patterns | Common agent patterns: proxy mode, Tasks integration, quality checks |
| schemas | YAML frontmatter schemas for agent/command files |
Agent File Structure
---
name: my-agent
description: When to use this agent with examples
model: sonnet # or opus, haiku
color: blue
tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit, Bash
---
# Agent Instructions
[System prompt and instructions here]
Key Patterns
External Model Integration
Orchestrators use Bash+claudish for external AI models:
claudish --model x-ai/grok-code-fast-1 --stdin --quiet \
< prompt.md > result.md
echo $? > result.exit
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 · 151 lines · 23 tokens per session scan A b42be604b7c0
agentdev-help is a command published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 777 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-30.
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.