Borrowing it
Nothing to install: this file belongs to joshstrange/bookorbit-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/joshstrange/bookorbit-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/joshstrange/bookorbit-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/joshstrange/bookorbit-mcp/claude-md)<a href="https://agentmods.dev/instructions/joshstrange/bookorbit-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/joshstrange/bookorbit-mcp/claude-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.02726 | $0.02726 |
| Opus 5 | $0.01363 | $0.01363 |
| Sonnet 5 | $0.00545 | $0.00545 |
| Haiku 4.5 | $0.00273 | $0.00273 |
Grade A, and why
bookorbit-mcp CLAUDE.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 8d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this is
An MCP (Model Context Protocol) server that exposes the text of ebooks stored in a self-hosted BookOrbit instance to LLMs. It is navigation-first: rather than dumping whole books into context, it lets a model find a book, inspect its chapter list, and pull only the pieces it needs.
Commands
npm install # install deps
npm run build # tsc -> dist/ (bin: dist/server.js)
npm run dev # run the server from source over stdio (tsx)
npm test # all unit tests (offline, against fixtures)
npm run typecheck # tsc --noEmit
npm run lint # eslint
npm run format # prettier --write .
npm run format:check # prettier --check . (CI enforces this)
# Run one test file:
node --import tsx --test test/html-to-text.test.ts
# Filter by test name:
node --import tsx --test --test-name-pattern="paginates" test/tools.test.ts
CI (.github/workflows/ci.yml) runs, in order: format:check → lint → typecheck → test → build.
Keep all five green.
Live checks (need a real server; read .env)
These hit a real BookOrbit instance and are not part of npm test:
node --import tsx scripts/smoke.mts # search -> parse -> chapter -> in-book search
node --import tsx scripts/mcp-check.mts # drives the BUILT server over the MCP stdio protocol
Config comes from env (or a local .env, gitignored — see .env.example): BOOKORBIT_URL,
plus either BOOKORBIT_USERNAME+BOOKORBIT_PASSWORD (preferred) or a static BOOKORBIT_TOKEN
(dev only). Optional CACHE_DIR.
Architecture (the big picture)
Request flow for a tool call:
tools.ts -> book-service.ts -> bookorbit-client.ts (HTTP to BookOrbit)
| -> epub-structure.ts (TOC/spine -> sections)
| -> html-to-text.ts (XHTML slice -> text)
+---------> cache.ts (disk, per bookId)
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.
- 8d ago First seen · 170 lines · 2,726 tokens per session scan A 19655563a09f
bookorbit-mcp CLAUDE.md is an instructions file published in the GitHub repository joshstrange/bookorbit-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 2,726 tokens to every session, about $0.0136 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
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.
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).
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).
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.
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.