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 instructions/batterworks/hatchdoor/agents-mdgit clone --depth 1 https://github.com/BatterWorks/HatchdoorWrote 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/instructions/batterworks/hatchdoor/agents-md)<a href="https://agentmods.dev/instructions/batterworks/hatchdoor/agents-md"><img src="https://agentmods.dev/badge/instructions/batterworks/hatchdoor/agents-md.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 | $0.01374 | $0.01374 |
| Opus 5 | $0.00687 | $0.00687 |
| Sonnet 5 | $0.00275 | $0.00275 |
| Haiku 4.5 | $0.00137 | $0.00137 |
Grade A, and why
Hatchdoor AGENTS.md 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 144 lines · 1,374 tokens per session scan A 848d2f7f8fe0
Hatchdoor AGENTS.md is an instructions file published in the GitHub repository BatterWorks/Hatchdoor (30 stars, last pushed 4d ago), licensed AGPL-3.0. It adds 1,374 tokens to every session, about $0.0069 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 instructions, from other repositories
siyuan AGENTS.md
AGENTS.md instructions for siyuan-note/siyuan, covering agents.md, 1. non-negotiable constraints, do not hand-edit, verification and prohibited operations and 2. project-specific rules.
obsidian-mcp-server AGENTS.md
Instructions for cyanheads/obsidian-mcp-server, covering agent protocol, what's next?, core rules, patterns and tool — obsidianlisttags.
hippocampus CLAUDE.md
Instructions for sturlese/hippocampus, covering layout, frontmatter schema, conventions, answering questions from the vault (read order) and contradictions.
data-olympus AGENTS.md
Instructions for knaisoma/data-olympus, covering data olympus, project overview, architecture, development workflow and code standards.
hippocampus AGENTS.md
Instructions for sturlese/hippocampus: Read and follow CLAUDE.md in the repository root completely before doing any work. It is the canonical project contract, written for Claude Code as the native host; its vault rules and workflows apply unchanged to Codex.
data-olympus copilot-instructions.md
Instructions for knaisoma/data-olympus: Read and follow all instructions in AGENTS.md. Read and follow all rules in .rules/. Read and follow the global Codex and Claude Code collaboration rule in /kn-projects/company-knowledge/tooling/codex-claude-collaboration.md.