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/hatch3r/hatch3r/hatch3r-quick-changegit 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-quick-change)<a href="https://agentmods.dev/commands/hatch3r/hatch3r/hatch3r-quick-change"><img src="https://agentmods.dev/badge/commands/hatch3r/hatch3r/hatch3r-quick-change.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.00024 | $0.08150 |
| Opus 5 | $0.00012 | $0.04075 |
| Sonnet 5 | $0.00005 | $0.01630 |
| Haiku 4.5 | $0.00002 | $0.00815 |
Grade A, and why
hatch3r-quick-change 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 — 490 lines — stays where its author put it; the contents beside it link to each section on GitHub.
§0 Detect Ambiguity (P8 B1)
Before any action, scan the user's change description for unresolved questions in scope, target files, irreversibility, or constraint conflicts (multiple matching files, missing acceptance criteria, unclear rename target, ambiguous "small" boundary). If any are found, ask the user via the platform-native question tool per agents/shared/user-question-protocol.md — do not proceed under silent assumption. This is the default path, not an exception. Acceptable to proceed without asking ONLY when the change is single-file, single-concern, and the brief alone is testable (typo, constant tweak, single-line edit). The Step 2c "ASK" rule remains in force for residual ambiguity discovered mid-workflow.
Agent Pipeline
| Stage | Agent(s) | Parallel | Required |
|---|---|---|---|
| 1. Scale Assessment | Orchestrator (inline) | No | Yes |
| 2. Implementation | hatch3r-implementer (nontrivial items) |
Per item | Nontrivial only |
| 3. Lint Fix | hatch3r-lint-fixer |
No | When lint/type errors |
| 4a. Review Loop | hatch3r-reviewer -> hatch3r-fixer (max 3 iterations) |
No (sequential) | Nontrivial only |
| 4b. Final Quality | hatch3r-testability + hatch3r-security |
Yes | Nontrivial code changes |
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.
Browser Automation
At the start of this command, ask the user once:
"Would you like to enable browser verification for this session? This uses Playwright to test changes in the running application."
Browser-verification contract (spec-first, tiered): see
commands/shared/orchestration-frame.md→ Browser Verification (opt-in); protocol homerules/hatch3r-browser-verification.md. Per-command slot: when enabled, the implementation (Step 4) and review (Step 6) stages run browser-verification steps on UI-affecting items; if declined, skip every browser-verification step for the session and do not re-ask.
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 · 490 lines · 24 tokens per session scan A b9e572aae907
hatch3r-quick-change is a command published in the GitHub repository hatch3r/hatch3r (26 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 8,150 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-09-03.
Other commands, from other repositories
diagnose-synapse
Run a comprehensive diagnostic of the SYNAPSE context engine, comparing expected vs. actual pipeline state, including session performance analysis with exact timing data.
debugger
Systematic debugging with TodoWrite and Memory integration.
investigate
Establish the proven causal chain for the target — from the observed symptom to the root cause that actually explains it — and write a report a fixer or planner can act on without repeating your work. You change nothing and fix nothing: the repository must be exactly as you found it when you finish. No one watches the…
review-errors
Find one defect: a real failure crosses the changed code and becomes indistinguishable from success to the caller, operator, or user who must react. Not every error needs logging; recovery is correct when the contract permits it and the right owner can still observe the outcome. Read-only: never modify files, commit…
manager
CRUD command router for managing SYNAPSE domains, rules, and star-commands.
todo-add.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.