Borrowing it
Nothing to install: this file belongs to agent-network-protocol/mcp2anp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agent-network-protocol/mcp2anp/main/AGENTS.mdgit clone --depth 1 https://github.com/agent-network-protocol/mcp2anpWrote 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/agent-network-protocol/mcp2anp/agents-md)<a href="https://agentmods.dev/instructions/agent-network-protocol/mcp2anp/agents-md"><img src="https://agentmods.dev/badge/instructions/agent-network-protocol/mcp2anp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/agent-network-protocol/mcp2anp/agents-md"><img src="https://agentmods.dev/badge/instructions/agent-network-protocol/mcp2anp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00588 | $0.00588 |
| Opus 5.5 | $0.00235 | $0.00235 |
| Sonnet 5.5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
mcp2anp 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 2mo 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
- Source code lives under
mcp2anp/, arranged intoadapters/,tools/, andcommon/; keep new runtime modules aligned with these boundaries. - Tests mirror the runtime tree in
tests/and share fixtures intests/fixtures/; reuse JSON-RPC payloads stored there instead of duplicating literals. - Store documentation and protocol notes in
docs/(notablydocs/spec.md), while diagrams, traces, and reference transcripts belong inassets/. - Example client scripts reside in
examples/; keep them minimal and cross-reference stable entry points such asmcp2anp.server.
Build, Test, and Development Commands
uv venv --python 3.11: create the canonical virtual environment before installing anything else.uv sync: install and lock dependencies frompyproject.toml; commit updateduv.lockanduv.tomlwhen they change.uv run python -m mcp2anp.server --reload: start the local bridge with hot reload for integration testing.uv run pytest [-k expr --maxfail=1]: run the full suite or narrow to a focused subset during debugging.
Coding Style & Naming Conventions
- Follow Google Python Style: four-space indentation, type hints on public APIs, English docstrings covering arguments, returns, and raised errors.
- Use
CamelCaseclasses,snake_casefunctions and variables, andUPPER_SNAKE_CASEconstants; keep module names short and descriptive. - Log through
loggingwith explicit context (IDs, endpoints) and keep inline comments in English; avoid stray prints.
Testing Guidelines
- Write
pytestmodules namedtest_<module>.pyalongside the unit under test; place reusable payloads in fixtures. - Target at least 90% statement coverage, covering success, failure, and boundary scenarios for each adapter.
- Include a fresh
uv run pytestsummary in every PR description; add regression tests when reproducing reported defects.
Commit & Pull Request Guidelines
- Craft imperative commit subjects under 72 characters; expand on complex changes with bullet points in the body.
- Reference issues with
Fixes:orRefs:trailers and flag breaking updates underBREAKING CHANGE:. - Open PRs with a concise summary, enumerated key changes, validation checklist (
uv run pytest, lint, manual run), and attach screenshots or logs for user-visible behavior.
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.
- 2mo ago First seen · 33 lines · 588 tokens per session scan A d66835e9b4c5
mcp2anp AGENTS.md is an instructions file published in the GitHub repository agent-network-protocol/mcp2anp (7 stars, last pushed 9mo ago), licensed MIT. It adds 588 tokens to every session, about $0.0024 per session on Opus 5.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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.