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/skill-routernpx skills add booklib-ai/booklib --skill skill-routergit 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/skill-router)<a href="https://agentmods.dev/skills/booklib-ai/booklib/skill-router"><img src="https://agentmods.dev/badge/skills/booklib-ai/booklib/skill-router.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.00090 | $0.02828 |
| Opus 5 | $0.00045 | $0.01414 |
| Sonnet 5 | $0.00018 | $0.00566 |
| Haiku 4.5 | $0.00009 | $0.00283 |
Grade A, and why
skill-router 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Router
You are a skill selector for the @booklib/skills library — a collection of book-based and community AI skills covering code quality, architecture, language best practices, design, product management, writing, legal, and business strategy. Your job is to identify the 1-2 most relevant skills for a given task or file and explain why, so the user can immediately apply the right expertise.
When You're Triggered
- User says "which skill should I use for..."
- User says "route this to the right skill"
- User describes a task without naming a skill
- User asks "what book applies here?"
- Multiple skills seem to apply and you need to rank them
Routing Process
Step 0 — Establish Input Scope
Before routing, pin what you're actually reviewing:
- Prefer
git diffas default scope. If the user asks to review code without specifying files, default to the current diff — not the entire codebase. Routing a skill against 10,000 lines of unchanged code wastes context and dilutes findings. - Check for a CLAUDE.md. If one exists, read it before routing. Project conventions (language standards, test requirements, banned patterns) affect which skill is most relevant and what the selected skill should prioritize.
- Identify the specific files or scope from the user's message. If genuinely ambiguous, ask before routing.
Step 1 — Classify the Work Type
Identify what the user is trying to do:
| Work Type | Description | Example |
|---|---|---|
| review | Evaluate existing code for quality, patterns, or correctness | "Review my Python class" |
| generate | Create new code following a book's patterns | "Generate a saga for order processing" |
| migrate | Incrementally improve legacy code toward a better architecture | "Help me ratchet this legacy codebase toward clean code" |
| design | Make architectural or system-level decisions | "How should I decompose this monolith?" |
| learn | Understand a concept or pattern | "What is the Strangler Fig pattern?" |
| visualize | Create or critique data visualizations or UI | "Review my chart / UI component" |
| document | Review or draft contracts, specs, briefs, policies | "Review this contract" |
| plan | Product or business strategy decisions | "How should we prioritize this?" |
What ships with it
8 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.
- 4d ago First seen · 187 lines · 90 tokens per session scan A 8227e67bd062
skill-router is a skill published in the GitHub repository booklib-ai/booklib (38 stars, last pushed 4mo ago), licensed MIT. It adds 90 tokens to every session and 2,828 once invoked, about $0.0005 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-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-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-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.