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/roberto-mello/lavra/agents-mdgit clone --depth 1 https://github.com/roberto-mello/lavraWrote 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/roberto-mello/lavra/agents-md)<a href="https://agentmods.dev/instructions/roberto-mello/lavra/agents-md"><img src="https://agentmods.dev/badge/instructions/roberto-mello/lavra/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.00004 | $0.00004 |
| Opus 5 | $0.00002 | $0.00002 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00000 |
Grade A, and why
lavra 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.
This is a copy
100% identical to superpowers AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
CLAUDE.md
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 · 1 lines · 4 tokens per session scan A 6ebdb617a810
lavra AGENTS.md is an instructions file published in the GitHub repository roberto-mello/lavra (50 stars, last pushed 2mo ago), licensed MIT. It adds 4 tokens to every session, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to superpowers AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
powercontext AGENTS.md
AGENTS.md instructions for oceanbase/powercontext, covering repository guidelines, project structure & module organization, build, test, and development commands, agent skills and coding style & naming conventions.
remind AGENTS.md
Instructions for sandst1/remind, covering remind - development guide for ai agents, project overview, architecture, key abstractions and data models (models.py).
attune-ai AGENTS.md
AGENTS.md instructions for Smart-AI-Memory/attune-ai, covering agents.md — attune ai, cross-provider collaboration, principles, shared truth and session protocol.
statewave-multi-agent-shared-context AGENTS.md
Instructions for smaramwbc/statewave-multi-agent-shared-context, covering statewave project memory, read it first and persist durable facts.
Traceplane AGENTS.md
Instructions for jaxxchen003/Traceplane, covering agents.md, 1. 实现顺序, 2. 绝对约束, 3. 保底字段 and 4. 模块边界.
wiii CLAUDE.md
Claude Code instructions for meiiie/wiii, a project described as: Wiii is an open-source durable AI workbench for conversations, local and cloud agents, files, tools, memory, artifacts, and permission-aware integrations.