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/langgenius/mosoo/agents-mdgit clone --depth 1 https://github.com/langgenius/mosooWhat 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.00115 | $0.00115 |
| Opus 5 | $0.00057 | $0.00057 |
| Sonnet 5 | $0.00023 | $0.00023 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
mosoo 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 2d 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
- Follow
CONTRIBUTING.mdfor setup, development, verification, generated files, Git/PR, migrations, and deployment. - For product behavior or module-boundary changes, read only the relevant PRD and architecture sections before editing.
- Production D1 is append-only: never reset production or rewrite an applied migration; follow
CONTRIBUTING.md#database-and-migrationsanddocs/production-deploy-verification.md. - Destructive or data-rewrite migrations require explicit user approval plus a backup and rollback plan.
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.
- 2d ago First seen · 7 lines · 115 tokens per session scan A e4061c6cd251
mosoo AGENTS.md is an instructions file published in the GitHub repository langgenius/mosoo (122 stars, last pushed 4d ago), licensed Apache-2.0. It adds 115 tokens to every session, about $0.0006 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
symphlo AGENTS.md
Instructions for huisezhiyin/symphlo, covering agents, read first, owner model, product boundaries and provenance and public-source rules.
agentdeck CLAUDE.md
Instructions for agentdecksdk/agentdeck, covering agentdeck, 1. product philosophy & north star, 2. architecture & layout, 3. engineering & coding standards and 4. verification gate & conventions.
Sponsio CLAUDE.md
Instructions for SponsioLabs/Sponsio, covering agent guide for sponsio, what sponsio is, positioning, what to read first and repository map.
devo AGENTS.md
Instructions for 7df-lab/devo, covering agents.md, rust, tests, test assertions and protocol and session settings.
mirage CLAUDE.md
Claude Code instructions for strukto-ai/mirage, covering claude.md, repo layout, typescript packages, python/typescript parity and module layout.
pi AGENTS.md
Instructions for TGYD-helige/pi, covering pi extensions monorepo — agent guidelines, project overview, required agent skills, ponytail — minimal-code discipline and mattpocock/skills — engineering workflow skills.