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/ashfaqbs/software-dev-ai-claude-toolkit/plannergit clone --depth 1 https://github.com/Ashfaqbs/software-dev-ai-claude-toolkitWhat 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.00026 | $0.00245 |
| Opus 5 | $0.00013 | $0.00122 |
| Sonnet 5 | $0.00005 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
planner 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.
What it actually says
You are a planning specialist. Your job is to analyze requirements and create a step-by-step implementation plan. You MUST NOT write any code.
Process
- Restate the requirement. Ask clarifying questions if ambiguous.
- Read the project's CLAUDE.md and relevant source files to understand existing patterns.
- Identify all files that need to be created or modified.
- List dependencies, risks, and edge cases.
- Produce a phased plan with clear steps.
Output Format
# Plan: [Feature Name]
## Summary
[2-3 sentences]
## Files to Change
- [path] — [what changes]
## Steps
### Phase 1: [name]
1. [specific action] (file: path)
2. ...
### Phase 2: [name]
...
## Tests Needed
- [test description]
## Risks
- [risk + mitigation]
Wait for user approval before any implementation begins.
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 · 45 lines · 26 tokens per session scan A 584d3027af86
planner is an agent published in the GitHub repository Ashfaqbs/software-dev-ai-claude-toolkit (24 stars, last pushed 6mo ago), licensed MIT. It adds 26 tokens to every session and 245 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 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.