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/rubysthedog/dotagents/agents-mdgit clone --depth 1 https://github.com/rubysthedog/dotagentsWhat 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.00100 | $0.00100 |
| Opus 5 | $0.00050 | $0.00050 |
| Sonnet 5 | $0.00020 | $0.00020 |
| Haiku 4.5 | $0.00010 | $0.00010 |
Grade A, and why
dotagents 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 yesterday.
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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 13 lines · 100 tokens per session scan A bc92323e01d4
dotagents AGENTS.md is an instructions file published in the GitHub repository rubysthedog/dotagents (2 stars, last pushed 2d ago), with no licence file. It adds 100 tokens to every session, about $0.0005 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
dotagents AGENTS.md
Instructions for bgreenwell/dotagents, covering agents.md, project purpose, context routing and validation.
varve CLAUDE.md
Instructions for varve-sh/varve, covering varve, memory tools, rules (always follow) and what actually happens when you call these tools.
engineering-memlog CLAUDE.md
Claude Code instructions for atazifor/engineering-memlog, covering engineering-memlog plugin — agent instructions, how the log gets into your context, search the log yourself when warranted, append a lesson after you work and plugin knobs (env vars).
THOR-memory-bible-for-AI AGENTS.md
AGENTS.md instructions for nworks3d/THOR-memory-bible-for-AI, covering agents.md - read this if you are the ai assistant, setting them up, the tools you have, how to write a note that actually comes back and after setup, this happens without you.
leptin AGENTS.md
AGENTS.md instructions for lionellau/leptin, covering leptin — for the agent, when to install yourself, install yourself (one block, unattended), how to use it (every session) and what to tell your human.
m_flow AGENTS.md
AGENTS.md instructions for FlowElement-xinliuyuansu/m_flow, covering m-flow — developer & agent reference, 1. repository map, extension points, 2. local development and python backend (requires python 3.10 – 3.13).