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/outlinedriven/odin-claude-plugin/agents-mdgit clone --depth 1 https://github.com/OutlineDriven/odin-claude-pluginWrote 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/outlinedriven/odin-claude-plugin/agents-md)<a href="https://agentmods.dev/instructions/outlinedriven/odin-claude-plugin/agents-md"><img src="https://agentmods.dev/badge/instructions/outlinedriven/odin-claude-plugin/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.02217 | $0.02217 |
| Opus 5 | $0.01108 | $0.01108 |
| Sonnet 5 | $0.00443 | $0.00443 |
| Haiku 4.5 | $0.00222 | $0.00222 |
Grade B, and why
odin-claude-plugin AGENTS.md scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Edit both carriers in place. Never commit them from this repository, and never stage `~/.codex/config.toml`; their owning repositories live outside this submodule. How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository contract
Repository file
Edit AGENTS.md, never CLAUDE.md. CLAUDE.md is a symlink, so replacing it forks the two files.
Canonical baseline
Make every persona or doctrine change in system-prompt-baseline.md first. It is the source of truth.
Propagate each canonical change to all six output styles: axiom-mode.md, builder.md, duet.md, linus.md, odin.md, and benchmark.md under plugins/odin-core/output-styles/. The Claude Code loader does not resolve references, so each style must embed the full baseline at its tail. Keep the span from the charter <role> through EOF byte-identical to system-prompt-baseline.md from <role> onward.
Perform propagation as one operation with one agent and one diff scope; never divide it by style.
Use the baseline generator; never hand-propagate the cascade:
- Edit
system-prompt-baseline.mdwithout changing an output style below its charter<role>. - Run
python3 scripts/sync-baseline.py. It replaces each style from its second<role>through EOF and preserves the persona preamble above it. - Run
python3 scripts/sync-baseline.py --check. Exit 0 means all styles match; exit 1 names drifted files; exit 2 means the canonical file or a required two-<role>layout is missing. - Stage and commit the canonical file and all six styles together.
Never hand-edit plugins/odin-core/output-styles/benchmark.md. Its margin-runner v0.5.5 header marks it as generated. The baseline generator may change only the embedded cascade below the runner preamble; a hand edit above that region requires explicit user authorization.
Submodule publishing
Commit and push from this repository, not its parent ~/.claude, because this tree is a Git
submodule. This checkout's .git is an unwritable submodule pointer, so git operations must run
in a clone inside .outline/worktree/<name>, never in /tmp, where work is easily lost.
Never force-push, and that includes every --force-with-lease variant: a lease protects the
remote from a stale overwrite and protects nothing from a rewrite you intended. On a branch with
an open pull request, rewriting history strands every inline review comment on commits that no
longer exist, and no permission error tells you that.
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 · +32 lines · +89 tokens per session 3e8298d6c2c4
- 5d ago First seen · 101 lines · 2,128 tokens per session scan B 1caa59527250
odin-claude-plugin AGENTS.md is an instructions file published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed today), licensed Apache-2.0. It adds 2,217 tokens to every session, about $0.0111 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).