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/automagik-dev/genie/claude-mdgit clone --depth 1 https://github.com/automagik-dev/genieWrote 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/automagik-dev/genie/claude-md)<a href="https://agentmods.dev/instructions/automagik-dev/genie/claude-md"><img src="https://agentmods.dev/badge/instructions/automagik-dev/genie/claude-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.1 | $0.06201 | $0.06201 |
| Opus 5 | $0.03100 | $0.03100 |
| Sonnet 5 | $0.01240 | $0.01240 |
| Haiku 4.5 | $0.00620 | $0.00620 |
Grade A, and why
genie CLAUDE.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 yesterday.
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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Genie CLI
Claude Code overlay: read and follow the canonical shared repository contract in AGENTS.md first. This file adds Claude-specific command and operational detail; shared rules belong in AGENTS.md.
Commands
bun run check # Full gate: typecheck + lint + dead-code + test
bun run build # Bundle to dist/genie.js (bun target, minified, single file)
bun run typecheck # tsc --noEmit
bun run lint # biome check .
bun run dead-code # bunx knip (has pre-existing false positives for biome/commitlint/husky)
bun test # All tests
bun test src/lib/wish-state.test.ts # Single file
Docs
docs/ is a symlink to .docs-vendor/genie/ where .docs-vendor is a git submodule of automagik-dev/docs (Mintlify, public site at automagik.dev). Engineers see and edit docs/ as if it were a regular subfolder of the genie repo — the submodule machinery is mostly invisible.
- Operator-facing pages (e.g.,
docs/installation.mdx,docs/security/key-rotation.mdx,docs/incident-response/canisterworm.mdx) appear on the public Mintlify site atautomagik.dev/genie/.... - Engineering-internal pages live under
docs/_internal/(architecture deep-dives, observability internals, agent-frontmatter contracts, CLI reference dumps, spawn-flow runbooks, detector specs). These are excluded from the public Mintlify build via**/_internal/inautomagik-dev/docs/.mintignore— visible inside the genie repo, hidden from public docs.
Workflow when editing docs:
# Make changes (the symlink follows into .docs-vendor/genie/)
$EDITOR docs/installation.mdx
# Commit + push the docs change to automagik-dev/docs
cd .docs-vendor
git checkout -b feat/<topic>
git add genie/installation.mdx
git commit -m "docs(genie): ..."
git push -u origin feat/<topic>
gh pr create --base main
# After the docs PR merges, bump the genie superproject pointer
cd .. # back to genie repo root
git submodule update --remote .docs-vendor
git add .docs-vendor
git commit -m "chore: bump .docs-vendor to docs main"
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.
- yesterday Changed · -7 lines · +207 tokens per session 1ccab4c30ff7
- 6d ago First seen · 244 lines · 5,994 tokens per session scan A bcbe91457a57
genie CLAUDE.md is an instructions file published in the GitHub repository automagik-dev/genie (334 stars, last pushed 2d ago), licensed MIT. It adds 6,201 tokens to every session, about $0.0310 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
apm python.instructions.md
Python development guidelines.
Commit Message
Comprehensive Conventional Commits guidelines for openwebui-extensions.
framework AGENTS.md
AGENTS.md instructions for ai-driven-dev/framework, covering agents.md, behavior, communication, action and memory management.
packmind packmind-rest-api-endpoint-design.instructions.md
Instructions for PackmindHub/packmind: Conventions for designing REST API endpoints that are predictable, self-documenting, and aligned with distinct business actions. Favors dedicated action endpoints over generic status updates, and rout... .
claude-crusts CLAUDE.md
Claude Code instructions for Abinesh-L/claude-crusts, covering identity, cli commands, rules, format and architecture.
Meterless AGENTS.md
Instructions for Meterless/Meterless, covering agent instructions for meterless, routing table, isolation rule, repo-wide rules and non-coding agents.