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/ashex/atproto-mcp/agents-mdgit clone --depth 1 https://github.com/Ashex/atproto-mcpWrote 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/ashex/atproto-mcp/agents-md)<a href="https://agentmods.dev/instructions/ashex/atproto-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/ashex/atproto-mcp/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.04114 | $0.04114 |
| Opus 5 | $0.02057 | $0.02057 |
| Sonnet 5 | $0.00823 | $0.00823 |
| Haiku 4.5 | $0.00411 | $0.00411 |
Grade A, and why
atproto-mcp 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
MCP server exposing a semantic-search knowledge base over AT Protocol docs,
lexicon schemas, Bluesky API docs, and cookbook examples. Python 3.12+,
FastMCP-style MCPServer (mcp SDK >=2.0) + txtai hybrid (BM25 + dense)
embeddings, stdio transport.
Commands
uv sync # install (uv-managed, hatchling build)
uv run atproto-mcp # run server over stdio
uv run mcp dev src/atproto_mcp/server.py # MCP Inspector
uv run python -m unittest discover -s tests -p 'test*.py' # test suite (what CI runs)
uv run python tests/smoke_test.py # manual end-to-end check (see gotcha below)
- No linter, formatter, or type-checker is configured. Match existing style by hand.
- CI (
.github/workflows/tests.yml) installs with plainpip install .on Python 3.12 and runs theunittestdiscover command above. pyproject.tomlrequires Python >=3.12 (matches README's "Python 3.12+" prerequisite).
Architecture
Startup flow (server.py): app_lifespan → Config.from_env() → publish
state.config → asyncio.create_task(_warmup(config)) → yield
immediately. Nothing slow runs on the startup path: a cold start clones four
repos and downloads a ~130MB model, far longer than a desktop host will wait
during the stdio handshake.
_warmup() then, off the startup path:
KnowledgeBase.load()viaasyncio.to_thread— before any network access, so a warm start serves in seconds even offline. On success it publishes withstate.commit_kb(kb, generation, save=False)(already on disk, do not rewrite) and sets statusready.fetch_all()to clone/refresh repos.- Cold start:
parse_all()+kb.build(save=False)+commit_kb(). Warm start: if the loaded index's repo SHAs (kb.indexed_shas) or embedding pipeline (kb.indexed_pipeline) differ from the current config, the live index keeps serving while_rebuild_index()builds a freshKnowledgeBaseviaasyncio.to_threadand commits it.
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.
- 4d ago First seen · 274 lines · 4,114 tokens per session scan A 4f6e04c41587
atproto-mcp AGENTS.md is an instructions file published in the GitHub repository Ashex/atproto-mcp (9 stars, last pushed 27d ago), licensed MIT. It adds 4,114 tokens to every session, about $0.0206 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.