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/arr-mcps/bookshelf-mcp/agents-mdgit clone --depth 1 https://github.com/arr-mcps/bookshelf-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/arr-mcps/bookshelf-mcp/agents-md)<a href="https://agentmods.dev/instructions/arr-mcps/bookshelf-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/arr-mcps/bookshelf-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.01385 | $0.01385 |
| Opus 5 | $0.00692 | $0.00692 |
| Sonnet 5 | $0.00277 | $0.00277 |
| Haiku 4.5 | $0.00138 | $0.00138 |
Grade A, and why
bookshelf-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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — bookshelf-mcp
MCP server exposing Bookshelf's v1 REST API (Readarr fork, OpenAPI 3.0.1) as tools so an LLM can read and manage a Bookshelf instance: authors, books, book files, editions, series, queue, history, indexers, import lists, custom formats, tags, commands, system status, and more. Full surface — reads and writes. Uses FastMCP, uv for deps.
Exposed as 15 resource-scoped portmanteau tools, not one tool per endpoint — see "Tool registry and the spec" below. A prior version registered all 221 endpoints individually; that blew the MCP context budget (~221 tools × ~250 tokens ≈ 55k tokens just for this one server) and has been retired.
Testing
- Offline suite:
make test(oruv run pytest) - Live integration (needs
BOOKSHELF_URL/BOOKSHELF_API_KEY):make test-integration- GET endpoints run against the live instance.
- POST/PUT/DELETE only run when
BOOKSHELF_WRITE_TESTS=1(safe create→update→delete cycles against a scratch tag, then cleanup). Never point write tests at a production library.
Tool registry and the spec
_TOOL_REGISTRYinbookshelf_mcp.pyis generated from the vendored spec attests/data/bookshelf_openapi.jsonbyscripts/generate_registry.py. It lists every JSON-producing endpoint under/api/v1plusGET /ping.- Excluded on purpose:
/login,/logout,/api(swagger metadata), static web routes, the.icscalendar feed, and binary/text endpoints (media covers, raw log files) —_reqJSON-decodes every response. - To add a tool or refresh coverage, edit
scripts/generate_registry.py(add NAME_OVERRIDES/DOC_OVERRIDES) and regenerate from the vendored spec, then re-run the tests. Do not hand-edit the registry. - Endpoint function naming (internal, no longer an MCP tool name):
bookshelf_<verb>_<resource>derived from path + method (e.g.bookshelf_list_author,bookshelf_create_author,bookshelf_delete_author,bookshelf_run_command). Overrides for flagship/action endpoints live in the authoring script.
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 · 55 lines · 1,385 tokens per session scan A 4141cf9bb80c
bookshelf-mcp AGENTS.md is an instructions file published in the GitHub repository arr-mcps/bookshelf-mcp (0 stars, last pushed 8d ago), licensed MIT. It adds 1,385 tokens to every session, about $0.0069 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
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 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.
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.
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).