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/evermind-ai/raven/agents-mdgit clone --depth 1 https://github.com/EverMind-AI/RavenWrote 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/evermind-ai/raven/agents-md)<a href="https://agentmods.dev/instructions/evermind-ai/raven/agents-md"><img src="https://agentmods.dev/badge/instructions/evermind-ai/raven/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.04878 | $0.04878 |
| Opus 5 | $0.02439 | $0.02439 |
| Sonnet 5 | $0.00976 | $0.00976 |
| Haiku 4.5 | $0.00488 | $0.00488 |
Grade A, and why
Raven 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.
How it starts
The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Raven AI-collaboration spec. Read this file before making any code change in this repo.
Scope: Codex / Claude Code / Claude API / any AI-assisted work. When a rule here conflicts with an ad-hoc instruction in conversation, this file wins — unless the user explicitly says "ignore rule X in AGENTS.md".
Hard constraints only (violations get reverted / rejected). Soft suggestions and style preferences belong in personal notes or conversation, not here. See the Maintenance note before adding sections — shorter is better.
| # | Section | Gist |
|---|---|---|
| 1 | Code comments | Don't comment unless necessary; comments in English |
| 2 | Branch naming | <type>/<snake_desc>; confirm base before cutting |
| 3 | Commits | Conventional Commits, all-English, Co-authored-by trailer |
| 4 | Dependencies | uv only — never pip / hand-edit lockfile |
| 5 | Tests | uv run pytest; strict file-naming |
| 6 | Domain terms | Consult CONTEXT-MAP.md before naming; use canonical terms |
| 7 | Repository assets | No report assets, web artifacts, or large files in PRs |
1. Code comments
§1.1 Top rule: don't add comments unless necessary
- Every new code file must document its purpose in English with an appropriate module docstring or equivalent file-level documentation. Inline comments still follow the necessity rules below.
- Match the style of surrounding lines. If neighboring code has no comments, don't add one to your new line.
- Comment only when:
- the logic is non-obvious;
- there's a hidden constraint (e.g. call-order sensitivity, a caller must do X first);
- you need to explain why, not what (the name already says what).
- Don't add comments that:
- describe what the code does (
# Increment counternext tocounter += 1); - mark edits (
# ← new/# changed this line); - reference a PR / Issue / locally-visible-only doc path (
# Refs: ...— invisible to others); - describe transient task context (
# For the X bug— stale once the task is done).
- describe what the code does (
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 · 376 lines · 4,878 tokens per session scan A 3606e3db3b29
Raven AGENTS.md is an instructions file published in the GitHub repository EverMind-AI/Raven (3,715 stars, last pushed 3d ago), licensed Apache-2.0. It adds 4,878 tokens to every session, about $0.0244 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
langgraph AGENTS.md
AGENTS.md instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
gptme AGENTS.md
AGENTS.md instructions for gptme/gptme, covering agent instructions for gptme, git workflow, code style, testing and project structure.
AstrBot copilot-instructions.md
Copilot instructions for AstrBotDevs/AstrBot, covering astrbot development instructions, working effectively, bootstrap and install dependencies, running the application and dashboard build (vue.js/node.js).
chatgpt-cli CLAUDE.md
Claude Code instructions for kardolus/chatgpt-cli, covering chatgpt-cli — release runbook, prerequisites, 1. cut the release, 2. publish the github release + binaries and 3. update the homebrew tap.
codexia AGENTS.md
AGENTS.md instructions for milisp/codexia, covering agents.md, project info, project tech, common commands and project structure.
rikkahub AGENTS.md
AGENTS.md instructions for rikkahub/rikkahub, covering repository guidelines, project overview, build, test, and development commands, module structure and concepts.