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.
git clone --depth 1 https://github.com/hatch3r/hatch3rWrote 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/hatch3r/hatch3r/hatch3r-bug-plan)<a href="https://agentmods.dev/commands/hatch3r/hatch3r/hatch3r-bug-plan"><img src="https://agentmods.dev/badge/commands/hatch3r/hatch3r/hatch3r-bug-plan.svg" alt="Measured on agentmods" 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.00031 | $0.06468 |
| Opus 5 | $0.00015 | $0.03234 |
| Sonnet 5 | $0.00006 | $0.01294 |
| Haiku 4.5 | $0.00003 | $0.00647 |
Grade A, and why
hatch3r-bug-plan 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 7d 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 — 486 lines — stays where its author put it; the contents beside it link to each section on GitHub.
§0 Detect Ambiguity (P8 B1)
Orchestration boilerplate: see
commands/shared/orchestration-frame.md→ §0 Detect Ambiguity (P8 B1). Triggers: contradictory inputs, missing target, unknown convention.
Agent Pipeline
| Stage | Agent(s) | Parallel | Required |
|---|---|---|---|
| 1. Research | hatch3r-researcher (4 parallel: symptom-trace, root-cause, impact-analysis, regression) |
Yes | Yes |
| 2. Document Generation | hatch3r-docs-writer (investigation report, ADRs) |
Yes | Yes |
| 3. Todo Generation | Orchestrator (inline) | No | Yes |
Parallel-safety conditions (per rules/hatch3r-agent-orchestration.md §Parallel Safety): every parallel fan-out above holds all three — read-only or disjoint writes (file- and contract-level), deterministic aggregation, no shared mutable state.
Bug Plan — Complex Bug Investigation from Symptom to Board-Ready Fix Items
Take a complex or ambiguous bug report and produce a structured investigation report (docs/investigations/), architectural decision records (docs/adr/) when the fix requires significant design choices, and structured todo.md entries (scoped fix items) ready for hatch3r-board-fill. Spawns parallel researcher sub-agents (symptom tracing, root cause investigation, impact assessment, regression research) to diagnose the bug from multiple angles before generating artifacts. AI proposes all outputs; user confirms before any files are written. Optionally chains into hatch3r-board-fill to create GitHub issues immediately.
When to use this command vs. the hatch3r-bug-fix skill:
- Use
hatch3r-bug-planwhen: root cause is unknown, multiple modules might be involved, reproducing is non-trivial, the bug has been lingering, or the fix may require phased work across multiple PRs. - Use
hatch3r-bug-fixskill directly when: root cause is clear, fix is localized, reproduction steps exist.
Shared Context
Read the hatch3r-board-shared skill at the start of the run if it exists. While this command does not perform board operations directly, it establishes patterns and context (GitHub owner/repo, tooling directives) that downstream commands like hatch3r-board-fill rely on. Cache any values found.
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.
- 7d ago First seen · 486 lines · 31 tokens per session scan A 92cb9934889f
hatch3r-bug-plan is a command published in the GitHub repository hatch3r/hatch3r (26 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 6,468 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-30.
Other commands, from other repositories
ui-smoke.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
refactor
Refactoring command. Detects code smells and creates a safe refactoring plan.
maintainer-review-test-coverage
Review the PR for test coverage — does new behavior have tests, are critical paths exercised, do existing tests still cover what they should (Pi-tuned).
CLAUDE
When debugging TUI commands like wt switch (interactive picker), use the tmux-cli skill (preferred) or MCP's node-terminal tools to test interactively.
drift-detect
Configuration drift detection command. Finds inconsistencies, orphaned components, and stale content in the Badi system.