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/diet103/claude-code-infrastructure-showcase/dev-docsgit clone --depth 1 https://github.com/diet103/claude-code-infrastructure-showcaseWhat 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.00485 |
| Opus 5 | $0.00005 | $0.00243 |
| Sonnet 5 | $0.00002 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
dev-docs 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 3d 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
You are an elite strategic planning specialist. Create a comprehensive, actionable plan for: $ARGUMENTS
Instructions
-
Analyze the request and determine the scope of planning needed
-
Examine relevant files in the codebase to understand current state
-
Create a structured plan with:
- Executive Summary
- Current State Analysis
- Proposed Future State
- Implementation Phases (broken into sections)
- Detailed Tasks (actionable items with clear acceptance criteria)
- Risk Assessment and Mitigation Strategies
- Success Metrics
- Required Resources and Dependencies
- Timeline Estimates
-
Task Breakdown Structure:
- Each major section represents a phase or component
- Number and prioritize tasks within sections
- Include clear acceptance criteria for each task
- Specify dependencies between tasks
- Estimate effort levels (S/M/L/XL)
-
Create task management structure:
- Create directory:
dev/active/[task-name]/(relative to project root) - Generate three files:
[task-name]-plan.md- The comprehensive plan[task-name]-context.md- Key files, decisions, dependencies[task-name]-tasks.md- Checklist format for tracking progress
- Include "Last Updated: YYYY-MM-DD" in each file
- Create directory:
Quality Standards
- Plans must be self-contained with all necessary context
- Use clear, actionable language
- Include specific technical details where relevant
- Consider both technical and business perspectives
- Account for potential risks and edge cases
Context References
- Check
PROJECT_KNOWLEDGE.mdfor architecture overview (if exists) - Consult
BEST_PRACTICES.mdfor coding standards (if exists) - Reference
TROUBLESHOOTING.mdfor common issues to avoid (if exists) - Use
dev/README.mdfor task management guidelines (if exists)
Note: This command is ideal to use AFTER exiting plan mode when you have a clear vision of what needs to be done. It will create the persistent task structure that survives context resets.
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.
- 3d ago First seen · 51 lines · 9 tokens per session scan A 2ef3e73a4b8c
dev-docs is a command published in the GitHub repository diet103/claude-code-infrastructure-showcase (10,016 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 485 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-30.
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.