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/aplaceforallmystuff/mcp-arr/agents-mdgit clone --depth 1 https://github.com/aplaceforallmystuff/mcp-arrWrote 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/aplaceforallmystuff/mcp-arr/agents-md)<a href="https://agentmods.dev/instructions/aplaceforallmystuff/mcp-arr/agents-md"><img src="https://agentmods.dev/badge/instructions/aplaceforallmystuff/mcp-arr/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.1 | $0.00811 | $0.00811 |
| Opus 5 | $0.00405 | $0.00405 |
| Sonnet 5 | $0.00162 | $0.00162 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
mcp-arr 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 6d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - mcp-arr
MCP server for the *arr media management suite (Sonarr, Radarr, Lidarr, Prowlarr).
Tech Stack
- Language: TypeScript
- Runtime: Node.js (ES modules)
- Protocol: Model Context Protocol (MCP)
- Build: TypeScript compiler (tsc)
Architecture
src/
├── index.ts # Server entry point, tool registration
├── tools/ # Tool implementations by service
│ ├── sonarr.ts # TV show management
│ ├── radarr.ts # Movie management
│ ├── lidarr.ts # Music management
│ └── prowlarr.ts # Indexer management
└── types.ts # Shared TypeScript types
Development Commands
# Build
npm run build
# Watch mode
npm run watch
# Test locally (requires env vars)
node dist/index.js
Environment Variables
| Variable | Required | Description |
|---|---|---|
| SONARR_URL | For Sonarr | Base URL (e.g., http://localhost:8989) |
| SONARR_API_KEY | For Sonarr | API key from Sonarr settings |
| RADARR_URL | For Radarr | Base URL |
| RADARR_API_KEY | For Radarr | API key |
| LIDARR_URL | For Lidarr | Base URL |
| LIDARR_API_KEY | For Lidarr | API key |
| PROWLARR_URL | For Prowlarr | Base URL |
| PROWLARR_API_KEY | For Prowlarr | API key |
Constraints
rules:
- id: no-hardcoded-urls
description: Never hardcode service URLs or API keys
check: All service access via environment variables
- id: consistent-tool-naming
description: Tool names follow pattern {service}_{action}
examples:
- sonarr_get_series
- radarr_search
- lidarr_get_albums
- id: error-handling
description: All API calls must handle errors gracefully
requirements:
- Check for missing env vars before API call
- Return meaningful error messages
- Don't expose raw API errors to users
- id: trash-guides-integration
description: TRaSH Guides tools use embedded guide data
note: Guide data fetched from trash-guides.info at runtime
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.
- 6d ago First seen · 117 lines · 811 tokens per session scan A 50b66f8087c0
mcp-arr AGENTS.md is an instructions file published in the GitHub repository aplaceforallmystuff/mcp-arr (207 stars, last pushed 2d ago), licensed MIT. It adds 811 tokens to every session, about $0.0041 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-30.
Other instructions, from other repositories
mcp-pihole AGENTS.md
Instructions for aplaceforallmystuff/mcp-pihole, covering agents.md - mcp-pihole, tech stack, architecture, environment variables and development.
mcp-pihole CLAUDE.md
Instructions for aplaceforallmystuff/mcp-pihole, a project described as: MCP server for Pi-hole v6 API - control DNS blocking from Claude Code.
mcp-pihole GEMINI.md
Instructions for aplaceforallmystuff/mcp-pihole, a project described as: MCP server for Pi-hole v6 API - control DNS blocking from Claude Code.
openrouter-mcp-multimodal AGENTS.md
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
AGENTS.md instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
cyxj-groksearch CLAUDE.md
Claude Code instructions for chenyuxiaojin/cyxj-groksearch, covering claude.md, 常用命令 and 结构与坑.