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/bryanlabs/mcp-ebook-server/agents-mdgit clone --depth 1 https://github.com/bryanlabs/mcp-ebook-serverWrote 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/bryanlabs/mcp-ebook-server/agents-md)<a href="https://agentmods.dev/instructions/bryanlabs/mcp-ebook-server/agents-md"><img src="https://agentmods.dev/badge/instructions/bryanlabs/mcp-ebook-server/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.00924 | $0.00924 |
| Opus 5 | $0.00462 | $0.00462 |
| Sonnet 5 | $0.00185 | $0.00185 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
mcp-ebook-server 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mcp-ebook-server
What it is
An MCP (Model Context Protocol) server that gives AI assistants direct access to an EPUB ebook library. Exposes tools for listing, reading, and searching books so AI can return verbatim text rather than hallucinated summaries.
Where it's used
Cluster: Deployed as Deployment mcp-ebook-server in the media-suite namespace. Image: ghcr.io/bryanlabs/mcp-ebook-server. The ebook library directory is mounted as a volume at /ebooks.
Local MCP: Run via Docker or pip and connect any MCP-compatible client (Claude, Cursor, Zed) to http://localhost:8080/mcp (streamable-http transport).
MCP surface
Tools:
| Tool | Purpose |
|---|---|
list_books() |
List all EPUBs in the library with title, author, language, relative path |
get_book_info(book_path) |
Metadata + full chapter list for a specific book |
get_chapter(book_path, chapter_number) |
Full text of a single chapter (1-indexed) |
get_chapters_range(book_path, start_chapter, end_chapter) |
Text of a chapter range, concatenated |
search_book(book_path, query) |
Case-insensitive search within one book; returns matches with context |
search_library(query) |
Search across all books; returns up to 5 matches per book |
Resource:
| Resource | Purpose |
|---|---|
health://status |
Returns JSON with status, library_path, and book_count |
How it works
- Transport: streamable-http via FastMCP (uvicorn/starlette). Listens on
0.0.0.0:8080. - Backend: No external service. Reads EPUB files directly from the mounted library directory using
ebooklibfor parsing andbeautifulsoup4/lxmlfor HTML-to-text extraction. - Supported formats: EPUB only. MOBI/AZW3 require prior conversion to EPUB. PDFs are not supported.
- Book path resolution: Accepts relative paths from library root, absolute paths, or bare filenames (fuzzy filename match).
- Caching: Parsed
EpubParserinstances are cached in memory per file path for the lifetime of the process.
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 · 73 lines · 924 tokens per session scan A 4d35072c693a
mcp-ebook-server AGENTS.md is an instructions file published in the GitHub repository bryanlabs/mcp-ebook-server (0 stars, last pushed 2mo ago), licensed MIT. It adds 924 tokens to every session, about $0.0046 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-09-01.
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.