Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/GantisStorm/essentials-claude-codenpx agentmods add commands/gantisstorm/essentials-claude-code/bug-plan-creatorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/gantisstorm/essentials-claude-code/bug-plan-creator)<a href="https://agentmods.dev/commands/gantisstorm/essentials-claude-code/bug-plan-creator"><img src="https://agentmods.dev/badge/commands/gantisstorm/essentials-claude-code/bug-plan-creator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/gantisstorm/essentials-claude-code/bug-plan-creator"><img src="https://agentmods.dev/badge/commands/gantisstorm/essentials-claude-code/bug-plan-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00018 | $0.00950 |
| Opus 5.5 | $0.00007 | $0.00380 |
| Sonnet 5.5 | $0.00004 | $0.00190 |
| Haiku 4.5 | $0.00002 | $0.00095 |
Grade A, and why
bug-plan-creator 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 1mo 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Investigation & Architectural Fix Planning
Investigate bugs from any input - error logs, stack traces, user reports. Creates an architectural fix plan with exact code specifications.
Use the right tool:
- Bug fixes →
/bug-plan-creator(this command) - New features/enhancements →
/plan-creator - Code quality improvements →
/code-quality-plan-creator
Note: Only view-only git commands allowed (no state modifications).
Arguments
Takes any input — error info, file paths, reference material:
- Error logs:
"TypeError: 'NoneType' at auth.py:45" - Stack traces:
"$(cat stacktrace.txt)" - Log files:
./logs/error.log - User reports:
"Login fails when user has no profile" - Diagnostic instructions:
"Check docker logs for api-service" - Reference files: pass a code map, design doc, or any file as additional context
Instructions
Step 1: Process Input
Parse $ARGUMENTS:
- If file path → use Read tool to load contents
- If inline text → extract error signals
- If diagnostic instructions → execute commands:
- Docker logs:
docker logs <container> --tail 500 - Process logs:
journalctl -u <service>
- Docker logs:
Step 2: Ask Clarifying Questions
Use AskUserQuestion to gather missing context. Ask only what's unclear — skip questions the user already answered in their input.
Questions to consider (ask 1-4 based on what's missing):
- Reproduction: Can you reproduce this? Always, intermittent, or specific conditions?
- Timeline: When did this start? Any recent changes (deploys, config, dependencies)?
- Impact: What's affected? Any workarounds currently in use?
- Environment: Any relevant environment details? (OS, versions, prod vs dev, config differences)
If the input is already detailed enough (clear error, obvious reproduction, sufficient context from logs), skip this step entirely and go straight to Step 3.
Step 3: Launch Agent
Assemble the enriched prompt from gathered logs/errors + clarifying answers. Launch background agent:
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.
- 1mo ago First seen · 114 lines · 18 tokens per session scan A 376a85b799de
bug-plan-creator is a command published in the GitHub repository GantisStorm/essentials-claude-code (90 stars, last pushed 8mo ago), licensed Unlicense. It adds 18 tokens to every session and 950 once invoked, about $0.0001 per session on Opus 5.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
map
Generate MAP.md — a relational map of every file, function, signature, and call in the repo.
sanity
Cross-check a dekko callers/uses result against a targeted grep before trusting a low/zero count.
doctor
Diagnose dekko environment/install issues (PATH shadowing, map freshness, MCP registration, plugin, hooks, CLAUDE.md policy block).
subagent-diagnose
Multi-agent failure-investigation orchestrator. Parallel to /subagent-implementation — same scratchpad + investigator + builder/surgeon + reviewer + FOLLOWUPS pattern — but starts from a failure, not a spec. Two modes share one loop: ci (failed CI run is the brief seed) and bug (freeform symptom paragraph is the brief…
quick-fix
Implement→review subagent loop with no planning phase, for a fix whose cause is known and whose shape is obvious, however many files it touches. No spec, no worktree, no docs or signals at the end; one audit. Routes to /subagent-diagnose on an unknown cause and to /atomic-plan on an open approach or contract choice.
debug
Systematic debugging with hypotheses and evidence gathering.