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/verygoodplugins/mcp-pirsch/agents-mdgit clone --depth 1 https://github.com/verygoodplugins/mcp-pirschWrote 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/verygoodplugins/mcp-pirsch/agents-md)<a href="https://agentmods.dev/instructions/verygoodplugins/mcp-pirsch/agents-md"><img src="https://agentmods.dev/badge/instructions/verygoodplugins/mcp-pirsch/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.00223 | $0.00223 |
| Opus 5 | $0.00112 | $0.00112 |
| Sonnet 5 | $0.00045 | $0.00045 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
mcp-pirsch 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.
What it actually says
MCP Pirsch contributor guide
Commands
Run npm run typecheck, npm run lint, npm test, and npm run build before handing off changes. Use npx -y @modelcontextprotocol/inspector@latest --cli node dist/index.js --method tools/list --format json for an MCP surface check.
Design constraints
- Keep the server stdio-only and read-only.
- Keep exactly four public tools unless the maintainers approve an API expansion.
- Tool handlers must declare Zod input/output schemas, read-only annotations, structured content, matching JSON text, and
isError: truefor expected failures. - Do not validate credentials at process start, select a domain automatically, return raw domain/account metadata, log secrets, or include raw upstream error bodies.
- Use
PIRSCH_DEFAULT_DOMAIN_IDonly as an explicit configured default; otherwise requiredomainId.
Delivery
Do not publish packages or registry entries from local work. The release workflow publishes a release tag to npm first, then the MCP Registry through GitHub OIDC.
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 · 18 lines · 223 tokens per session scan A 51c88aae443f
mcp-pirsch AGENTS.md is an instructions file published in the GitHub repository verygoodplugins/mcp-pirsch (1 stars, last pushed 7d ago), licensed MIT. It adds 223 tokens to every session, about $0.0011 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
openrouter-mcp-multimodal AGENTS.md
Instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
Plonk AGENTS.md
Instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
mcp-dockhand copilot-review.instructions.md
Instructions for strausmann/mcp-dockhand: When reviewing pull requests in this repository.
cyxj-groksearch CLAUDE.md
Instructions for chenyuxiaojin/cyxj-groksearch, covering claude.md, 常用命令 and 结构与坑.
minecraft-dev-mcp AGENTS.md
Instructions for MCDxAI/minecraft-dev-mcp, covering agent handbook – minecraft dev mcp, project snapshot, what agents should prioritize, architecture wayfinder (src/) and available mcp tools (for llm surfaces).
bray AGENTS.md
AGENTS.md instructions for forgesworn/bray, covering agents.md — nostr-bray, what this is, build & test, architecture and tool groups.