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/toruai/megg/claude-mdgit clone --depth 1 https://github.com/ToruAI/meggWrote 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/toruai/megg/claude-md)<a href="https://agentmods.dev/instructions/toruai/megg/claude-md"><img src="https://agentmods.dev/badge/instructions/toruai/megg/claude-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.1 | $0.00059 | $0.00059 |
| Opus 5 | $0.00030 | $0.00030 |
| Sonnet 5 | $0.00012 | $0.00012 |
| Haiku 4.5 | $0.00006 | $0.00006 |
Grade A, and why
megg 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 5d 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
Spec Instructions
Specs live in .ai/specs/. See AGENTS.md for the index.
Before implementing anything non-trivial, read the relevant spec.
For new features: draft spec in .ai/changes/ first (see /openspec-workflow skill).
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.
- 5d ago First seen · 6 lines · 59 tokens per session scan A 07c0c3e4b6ec
megg CLAUDE.md is an instructions file published in the GitHub repository ToruAI/megg (5 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session, about $0.0003 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
Perenna AGENTS.md
Instructions for scarletkc/Perenna, covering perenna agent guidelines, start with the project contract, environment, implementation boundaries and generated and versioned artifacts.
nobrainr CLAUDE.md
Claude Code instructions for vicquick/nobrainr, covering nobrainr — collective agent memory service, what this is, canonical categories, architecture and routing (when using a reverse proxy).
mcp-memory-server CLAUDE.md
Instructions for foxj77/mcp-memory-server, covering claude.md, what this repo is, chart layout, build / run / test and local build + run.
mem0-mcp-selfhosted CLAUDE.md
Instructions for elvismdev/mem0-mcp-selfhosted, covering claude.md, mcp servers, build & test commands and architecture.
Muninn GEMINI.md
Gemini CLI instructions for wjohns989/Muninn, covering muninn mcp — sota+ development context, 🚀 sota+ development philosophy, 🛠 operational guidelines (always-on), 🏗 system architecture and 📂 project structure.
flux-memory CLAUDE.md
Instructions for harsh5i/flux-memory, covering flux memory v0.5 — claude.md, hard constraints (never deviate), repo layout, development rules and status.