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/komga-mcp/agents-mdgit clone --depth 1 https://github.com/arr-mcps/komga-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/komga-mcp/agents-md)<a href="https://agentmods.dev/instructions/arr-mcps/komga-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/arr-mcps/komga-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.01221 | $0.01221 |
| Opus 5 | $0.00611 | $0.00611 |
| Sonnet 5 | $0.00244 | $0.00244 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
komga-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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — komga-mcp
MCP server exposing Komga's REST API as tools for browsing and managing comic, manga, BD, magazine, and ebook libraries. Uses FastMCP, uv for deps.
Exposed as 8 resource-scoped portmanteau tools, not one tool per endpoint — see "Portmanteau registration" below. A prior version registered all 81 endpoints individually; that blew the MCP context budget (~81 tools × ~250 tokens ≈ 20k tokens just for this one server) and has been retired.
Testing
- Offline suite:
make test(oruv run pytest) - Live integration (needs
KOMGA_URL/KOMGA_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> - Then sync the project copy:
cd /home/savagecore/Documents/christopfarr/mcp/komga-mcp git fetch origin && git reset --hard origin/main - 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/komga-mcp && git fetch origin && git reset --hard origin/main' ssh [email protected] -- 'cd /root/komga-mcp && uv tool install --force .'uv tool install→/root/.local/bin/komga-mcp(not from the repo).
Env note
All tools go through Komga's REST API keyed on KOMGA_API_KEY. Keep API keys out of code, logs, and commit messages. Responses are returned without reshaping so an MCP client can use the same information as Komga's own web client. 33 operations carry a "Requires ADMIN" / "Requires the Komga ADMIN role" note in their docstring — this is documentation-only (Komga itself enforces the role via a 403; nothing here checks it). Those notes survive automatically in each group tool's per-operation description since the underlying functions and their docstrings are unchanged by the portmanteau refactor.
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 · 46 lines · 1,221 tokens per session scan A 2f0cb626fde5
komga-mcp AGENTS.md is an instructions file published in the GitHub repository arr-mcps/komga-mcp (0 stars, last pushed 11d ago), licensed MIT. It adds 1,221 tokens to every session, about $0.0061 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).