Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/arr-mcps/tracearr-mcp/agents-md)<a href="https://agentmods.dev/instructions/arr-mcps/tracearr-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/arr-mcps/tracearr-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.1 | $0.00766 | $0.00766 |
| Opus 5 | $0.00383 | $0.00383 |
| Sonnet 5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
tracearr-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 5d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — tracearr-mcp
MCP server exposing Tracearr's Public API v2 (REST, read-only) as tools so an LLM can query Plex, Jellyfin, and Emby monitoring data: watch history, active streams, media, users, libraries, and recently added items. Uses FastMCP, uv for deps.
Testing
- Offline suite:
make test(oruv run pytest) - Live integration (needs
TRACEARR_URL/TRACEARR_API_KEY):make test-integration
Release workflow
Always use the make bump-* targets to bump the version (uv version --bump patch|minor|major), which updates pyproject.toml and uv.lock together. Do NOT edit the version by hand.
- Bump:
make bump-patch(orbump-minor/bump-major) - Commit message is just the version, e.g.
0.1.2— nothing else. - Tag it
v<version>(e.g.v0.1.2). - Push main and the tag:
git push origin main git push origin v<version> - Deploy to the Proxmox host (root SSH key): pull the repo then reinstall the uv tool:
The host runs it viassh [email protected] -- 'cd /root/tracearr-mcp && git fetch origin && git reset --hard origin/main' ssh [email protected] -- 'cd /root/tracearr-mcp && uv tool install --force .'uv tool install→/root/.local/bin/tracearr-mcp(not from the repo). There is no/home/savagecore/Documents/christopfarr/mcp/tracearr-mcpcopy.
Read-only note
The Tracearr Public API has no write surface. Every tool is read-only (readOnlyHint=True) — never introduce a tool that writes or deletes. Keep the whole server in tracearr_mcp.py unless it outgrows it.
Tool count: this server is the one deliberate exception to the portmanteau standard
Every other server in the arr-mcps fleet exposes ~5-15 resource-scoped
portmanteau tools (an operation enum dispatching to per-endpoint
functions) instead of one MCP tool per REST endpoint — see the masterlist's
AGENTS.md for the full pattern and the rationale (hundreds of individually
registered tools blow the MCP context budget on session start). This server
is the single exception: at 13 tools it's already comfortably under the
ceiling that pattern exists to enforce, so converting it would add a
dispatch-by-string indirection layer for zero context-budget benefit. Do
not convert it just for consistency.
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.
- 5d ago First seen · 48 lines · 766 tokens per session scan A 0e163c7703c9
tracearr-mcp AGENTS.md is an instructions file published in the GitHub repository arr-mcps/tracearr-mcp (0 stars, last pushed 11d ago), licensed MIT. It adds 766 tokens to every session, about $0.0038 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).
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.
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).
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.
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.
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.