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/giggsoinc/raven/agents-mdgit clone --depth 1 https://github.com/giggsoinc/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/giggsoinc/raven/agents-md)<a href="https://agentmods.dev/instructions/giggsoinc/raven/agents-md"><img src="https://agentmods.dev/badge/instructions/giggsoinc/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.00999 | $0.00999 |
| Opus 5 | $0.00500 | $0.00500 |
| Sonnet 5 | $0.00200 | $0.00200 |
| Haiku 4.5 | $0.00100 | $0.00100 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Grok / Codex / Cursor boot
Codex also reads AGENTS.override.md first (same directory). Do not skip it.
First load (same UX every IDE)
python3 scripts/ops/raven-first.py --boot(rebuild + open once). Fallback:python3 "${CLAUDE_PLUGIN_ROOT}/scripts/ops/raven-first.py" --boot. Printhost=rules=memory=load=educate=route=expected_route=first_load=.- If
load=1, Read only thememory=card. Ifload=0, no vault, no invented memory. python3 scripts/ops/raven-first.py --session-start— print that banner (version, host, rules, educate, expected SIMPLE/MEDIUM/COMPLEX).- Later turns: do not re-open the dashboard unless they ask (raven dashboard /
/raven-dashboard→ide-boot.py --open).
0. BEFORE any answer or tool — every user turn. No exemptions.
- Run
python3 scripts/ops/raven-first.py --prompt "<their full message>"first. Fallback:python3 "${CLAUDE_PLUGIN_ROOT}/scripts/ops/raven-first.py" --prompt "<their full message>". That write fills dashboard Logs. Skipping it leaves Logs empty for this IDE. - Do not lead with
bash scripts/raven-python.shas the only path — Codex in a public app repo often has no wrapper until raven-first copies the engine from the plugin root. - There is no “direct path” that skips this. Not git log, git status, “what shipped”, smoke tests, or “I didn’t need the router.” Claude PreToolUse denies other tools without
.raven/.route-stamp. Codex/Cursor/AntiGravity/Grok have no that hook — empty dashboard Logs = you skipped. That is the proof, not a design exemption. - Line 1 = printed
🔀 Router · … - Line 2 = printed
💰 total-cost= last_turn= est= - Line 3 = printed
educate= guided|offandexpected=<recommend model> - Line 4 =
session=<the model writing this> - Line 5 =
Intent: plan|debug|direct — {why} - Then tools/answer. Spawn SIMPLE-tier if this IDE can. Do not only print the toast.
- Recap:
python3 scripts/ops/raven-first.py --end→💰 turn= total-cost=(or?if Stop has not priced yet).
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 · 34 lines · 999 tokens per session scan A 79705bb7133c
raven AGENTS.md is an instructions file published in the GitHub repository giggsoinc/raven (5 stars, last pushed 2d ago), licensed MIT. It adds 999 tokens to every session, about $0.0050 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-31.
Other instructions, from other repositories
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.