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/kychee-com/run402/claude-mdgit clone --depth 1 https://github.com/kychee-com/run402What 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.00219 | $0.00219 |
| Opus 5 | $0.00110 | $0.00110 |
| Sonnet 5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
run402 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 3d 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.
What it actually says
@AGENTS.md
Git workflow — worktrees, never branches
Multiple agent sessions work these repos in parallel. Isolation is by git worktree, not by branching or stashing.
- ALWAYS worktree. Do work inside a dedicated worktree (
git worktree add). Never edit, branch-switch, or otherwise disturb a shared checkout — another session may be using it, and switching branches under them destroys their work. - NEVER create branches. No feature-branch or PR ceremony on your own initiative. A worktree's auto-created backing branch is plumbing, not workflow.
- NEVER
git stash. It is invisible to everyone else and easy to lose. - Small changes commit directly to
main, no ceremony. From a worktree, push withgit push origin HEAD:main(expect to rebase). - If you find yourself on a branch in a primary checkout, you are already in the wrong place — make a worktree and clean up after yourself.
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.
- 3d ago First seen · 18 lines · 219 tokens per session scan A 156515593727
run402 CLAUDE.md is an instructions file published in the GitHub repository kychee-com/run402 (24 stars, last pushed 3d ago), licensed MIT. It adds 219 tokens to every session, about $0.0011 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
xenarch-mcp CLAUDE.md
Claude Code instructions for xenarch-ai/xenarch-mcp, covering xenarch-mcp, structure, stack, commands and design principle.
appwrite AGENTS.md
AGENTS.md instructions for appwrite/appwrite, covering appwrite, commands, stack, layout and libraries.
mcp-server-excel coverage-prevention-strategy.instructions.md
Instructions for sbroenne/mcp-server-excel, covering generated surface coverage, contract change workflow, required checks and common incomplete changes.
llm-context.py CLAUDE.md
Instructions for cyberchitta/llm-context.py, covering claude.md, working notes (gitignored) and draining the field notes.
openrouter-mcp-multimodal AGENTS.md
Instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
autotask-mcp dev_workflow.instructions.md
Guide for using Taskmaster to manage task-driven development workflows.