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/rules/hatch3r/hatch3r/hatch3r-clarification-default)<a href="https://agentmods.dev/rules/hatch3r/hatch3r/hatch3r-clarification-default"><img src="https://agentmods.dev/badge/rules/hatch3r/hatch3r/hatch3r-clarification-default.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.02114 | $0.02114 |
| Opus 5 | $0.01057 | $0.01057 |
| Sonnet 5 | $0.00423 | $0.00423 |
| Haiku 4.5 | $0.00211 | $0.00211 |
Grade A, and why
hatch3r-clarification-default 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 4d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hatch3r Clarification Default
Pillars: P8 (Clarification & Fan-out Discipline)
Canonical reference for the how of asking: agents/shared/user-question-protocol.md. This rule governs the whether — it is the corpus-wide, always-on floor that every adapter ships to the end-user repo, so B1 enforcement does not depend on per-artifact body inheritance alone.
B1 directive (verbatim)
Every hatch3r-invoked agentic workflow detects and resolves ambiguity via
agents/shared/user-question-protocol.mdBEFORE executing — default behavior, not exception-driven.
Default-path, not exception: a workflow that proceeds without resolving a live trigger below has violated B1, even if it later succeeds. Asking is the baseline; silent assumption is the deviation that must be justified.
Five-trigger set
Apply the protocol before any write-tool invocation when ANY of these hold:
- Ambiguous scope — the request maps to two or more reasonable interpretations that produce different artifacts.
- Multiple valid interpretations — two or more viable approaches with materially different cost, scope, or risk.
- Irreversible action — deleting an artifact, renaming a public artifact id, dropping a frontmatter field, force-pushing a branch.
- Missing acceptance criteria — no testable definition of done for the requested change.
- Unattested product decision — the change destroys or transforms user data, or alters user-visible behavior beyond stated acceptance criteria, with no user statement authorizing it; an agent-authored comment or PR sentence is self-certification, not authorization.
If none of the five hold and the safer default is obvious and reversible, proceed and note the default — do not manufacture a question (anti-pattern per agents/shared/user-question-protocol.md "Echo-as-question").
§0 ambiguity gate (every mutating artifact)
Every artifact under agents/, commands/, and skills/ that can mutate files MUST carry a §0 (or "Step 0 — Ambiguity gate") block as its first procedural step. The block:
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.
- 4d ago First seen · 85 lines · 2,114 tokens per session scan A 402e14383b2d
hatch3r-clarification-default is a cursor rule published in the GitHub repository hatch3r/hatch3r (26 stars, last pushed 3d ago), licensed MIT. It adds 2,114 tokens to every session, about $0.0106 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 cursor rules, from other repositories
data-engineer
AIOX agent @data-engineer - Database Architect & Operations Engineer.
devops
AIOX agent @devops - GitHub Repository Manager & DevOps Specialist.
architect
AIOX agent @architect - Architect.
squad-creator
AIOX agent @squad-creator - Squad Creator.
ux-design-expert
AIOX agent @ux-design-expert - UX/UI Designer & Design System Architect.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.