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 skills/booklib-ai/booklib/booklib-mcp-guidenpx skills add booklib-ai/booklib --skill booklib-mcp-guidegit clone --depth 1 https://github.com/booklib-ai/booklibWrote 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/skills/booklib-ai/booklib/booklib-mcp-guide)<a href="https://agentmods.dev/skills/booklib-ai/booklib/booklib-mcp-guide"><img src="https://agentmods.dev/badge/skills/booklib-ai/booklib/booklib-mcp-guide.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.00036 | $0.01246 |
| Opus 5 | $0.00018 | $0.00623 |
| Sonnet 5 | $0.00007 | $0.00249 |
| Haiku 4.5 | $0.00004 | $0.00125 |
Grade A, and why
booklib-mcp-guide 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BookLib MCP Tool Guide
BookLib exposes 5 MCP tools to AI coding agents. Each tool has a single purpose. This guide covers when to call each one, what parameters to pass, and common workflows.
Tool Reference
| Tool | When to call | Key params |
|---|---|---|
lookup |
Before working with unfamiliar APIs or post-training deps | query (required), file, limit, source |
review |
User asks for deep code review of a specific file | skill_name, file_path (both required) |
remember |
User says "remember this", "capture", or makes a team decision | title (required), content, type, tags |
verify |
After writing code that uses unfamiliar or new APIs | file_path (required) |
guard |
After writing code that touches architecture or API choices | file_path (required) |
Decision Tree
Need current docs for a post-training library -> lookup
Need a full expert review of a file -> review
User wants to save a decision or insight -> remember
Code uses unknown imports -> verify
Code might violate team rules -> guard
Tool Details
lookup
Searches across post-training corrections, team knowledge, and expert skills. Returns structured principles with source citations.
Parameters:
query(string, required): What you need to know. Include the library name and task.file(string): Path to the file being worked on. Adds language and component context.limit(number): Maximum results. Default: 3.source(enum: all/skills/knowledge): Filter by source type.
Prioritization order: (1) post-training gap corrections, (2) team knowledge nodes, (3) expert skill principles.
review
Audits a file against a named skill's principles. Returns structured findings with line references and citations.
Parameters:
skill_name(string, required): The skill to review against (e.g., "effective-kotlin", "clean-code-reviewer").file_path(string, required): Path to the file to review.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 130 lines · 36 tokens per session scan A 37ae5ad73aca
booklib-mcp-guide is a skill published in the GitHub repository booklib-ai/booklib (38 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,246 once invoked, about $0.0002 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-30.
Other skills, from other repositories
project-spine-kickoff
Use when the user wants to set up Project Spine for a new project — phrases like "new client project", "kickoff", "create AGENTS.md from scratch", "generate agent instructions for this repo", "set up project context". Runs spine init → edits brief → spine compile → reviews outputs. For stale files use…
project-spine
Use when the user mentions AGENTS.md, CLAUDE.md, copilot-instructions, Cursor rules, project brief, context for coding agents, agency kickoff, onboarding a new project, or asks "how do I set up Project Spine". This is the orientation skill — reach for it FIRST when the user's intent involves Project Spine, then chain…
project-spine-drift
Use when the user mentions drift, says AGENTS.md / CLAUDE.md / copilot-instructions / Cursor rules are "stale" or "out of date", asks about CI catching docs drift, or says "check if my spine is still current". Runs spine drift check, interprets each drift category, and guides resolution. For initial setup use…
project-spine-rationale
Use when the user wants to review, polish, or share the generated Project Spine rationale file locally. Phrases like "show the project rationale", "send the client a project summary", "review rationale.md", or "make the client-facing overview safer".
project-spine-template
Use when the user wants to apply a bundled, user-local, or project-local template to a new project, or save the current project as a reusable template. Phrases like "use our agency starter", "save this as a template for future clients", "apply the shared saas-marketing starter".
project-spine-workspace
Use when the user asks about Project Spine hosted workspaces, team sync, shared workspace templates, invites, or commands such as spine login, spine workspace, spine publish, or spine drift check --push.