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/mythicagents/sage/agents-mdgit clone --depth 1 https://github.com/MythicAgents/sageWrote 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/mythicagents/sage/agents-md)<a href="https://agentmods.dev/instructions/mythicagents/sage/agents-md"><img src="https://agentmods.dev/badge/instructions/mythicagents/sage/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.10388 | $0.10388 |
| Opus 5 | $0.05194 | $0.05194 |
| Sonnet 5 | $0.02078 | $0.02078 |
| Haiku 4.5 | $0.01039 | $0.01039 |
Grade A, and why
sage 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 550 lines · 10,388 tokens per session scan A 80bd5ab698e3
sage AGENTS.md is an instructions file published in the GitHub repository MythicAgents/sage (21 stars, last pushed 7d ago), licensed GPL-3.0. It adds 10,388 tokens to every session, about $0.0519 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
CookHero copilot-instructions.md
Instructions for Decade-qiu/CookHero, covering global instructions, 0. general code quality requirements, 1. task decomposition & planning, 2. version compatibility policy and 3. git operations.
deepagents AGENTS.md
AGENTS.md instructions for langchain-ai/deepagents, covering global development guidelines for the deep agents monorepo, corridor security analysis, development workflow, suppressing ruff rules and pr conventions.
openagent CLAUDE.md
Claude Code instructions for the-open-agent/openagent, covering claude.md, commands, architecture, backend (go / beego) and frontend (react).
langchain-aws AGENTS.md
Instructions for langchain-ai/langchain-aws, covering global development guidelines for the langchain monorepo, project architecture and context, langchain-aws structure, key components and langgraph-checkpoint-aws structure.
Swarm AGENTS.md
Instructions for christopherkarani/Swarm, covering agent instructions, public repository hygiene and development rules.
TradingAgents-Telegram CLAUDE.md
Instructions for IvanWng97/TradingAgents-Telegram, covering tradingagents-telegram — architecture reference, layout, architecture (for code reviewers), request lifecycle (manual /watch tap) and state ownership.