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/lolaplex/agents-docs/agents-mdgit clone --depth 1 https://github.com/Lolaplex/agents-docsWhat 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.00167 | $0.00167 |
| Opus 5 | $0.00084 | $0.00084 |
| Sonnet 5 | $0.00033 | $0.00033 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
agents-docs 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.
What it actually says
AGENTS.md — agents-docs Developer Guidelines
Architecture Principles
- Zero Heavy Dependencies: Pure Python standard library +
mcp>=1.0.0,<2. No vector DBs, no embeddings, no bloated HTTP frameworks. - Filesystem-First: All docsets reside in
~/.agents/docs/<name>/. Plain markdown, human-readable, editable. - Header-Aware BM25: Section parsing uses
#,##,###headers to preserve code block integrity.
Commands
- Run test suite:
python tests/run_all_tests.py - Sync bundled assets:
python scripts/sync_bundled.py - Test CLI:
python -m agents_docs catalog - Start FastMCP:
python -m agents_docs serve
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 · 167 tokens per session scan A 6909fe96bcf6
agents-docs AGENTS.md is an instructions file published in the GitHub repository Lolaplex/agents-docs (2 stars, last pushed 9d ago), licensed MIT. It adds 167 tokens to every session, about $0.0008 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
agent-skills AGENTS.md
Instructions for addyosmani/agent-skills, covering agents.md, repository overview, opencode integration, core rules and intent → skill mapping.
gortex CLAUDE.md
Claude Code instructions for zzet/gortex, covering gortex, build & test, codebase overview, discovery (read once, then keep using) and llm provider (powers ask and searchsymbols assist: modes).
peon-ping GEMINI.md
Instructions for PeonPing/peon-ping, covering gemini.md - peon-ping, project overview, main technologies, architecture and building and running.
awesome-copilot-id AGENTS.md
Instructions for GulajavaMinistudio/awesome-copilot-id, covering communication, explanation and documentation, markdown formatting, user communication style and workflow & methodology.
free-ai-gateway AGENTS.md
Instructions for zaber-dev/free-ai-gateway, covering 🤖 free-ai gateway - agentic development guidelines, 🏛️ monorepo architecture & package boundaries, 🛑 strict architectural rules for agents, 💻 essential developer commands and build all packages across monorepo.
codevira CLAUDE.md
Instructions for sachinshelke/codevira, covering codevira — persistent project memory, when to call which codevira tool, at the start of every session, before modifying any file and before adopting a pattern, library, or naming convention.