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 skills add JayRHa/AgentSkills --skill book-summarizergit clone --depth 1 https://github.com/JayRHa/AgentSkillsWrote 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/jayrha/agentskills/book-summarizer)<a href="https://agentmods.dev/skills/jayrha/agentskills/book-summarizer"><img src="https://agentmods.dev/badge/skills/jayrha/agentskills/book-summarizer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jayrha/agentskills/book-summarizer"><img src="https://agentmods.dev/badge/skills/jayrha/agentskills/book-summarizer.svg" alt="Reviewed on agentmods" width="80" 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.00112 | $0.01064 |
| Opus 5.5 | $0.00045 | $0.00426 |
| Sonnet 5.5 | $0.00022 | $0.00213 |
| Haiku 4.5 | $0.00011 | $0.00106 |
Grade A, and why
book-summarizer 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 1mo 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Book Summarizer
Overview
This skill produces a faithful, well-structured summary of a book at the requested depth — a one-line gist, an executive summary, key takeaways, or chapter-by-chapter notes — capturing the central thesis, the supporting ideas, the most memorable examples, and what the reader can actually do with it.
Keywords: book summary, key takeaways, TL;DR, main idea, chapter summary, executive summary, book notes, book club, nonfiction, study notes.
When to use vs. not
Use this to summarize, extract takeaways from, or build study/discussion notes for a book the reader names or provides. Accuracy first: if you don't actually know a book's content, say so rather than inventing — never fabricate quotes, statistics, or plot points. For very recent or obscure titles, ask the user to paste text or confirm details. Note that a summary is no substitute for reading when nuance matters (e.g., for academic citation).
Inputs to gather first
- The book (title + author — confirm you have the right one).
- Depth wanted — one-liner, ~1 page, key takeaways, or chapter-by-chapter.
- Purpose — decide whether to read it, apply it, prep a discussion, study for an exam, or recall it.
- Fiction or nonfiction (changes the structure — themes/plot vs. thesis/arguments).
- Spoiler tolerance for fiction.
Workflow
- Confirm the book and your confidence. State the title/author and that you can summarize it accurately. If unsure, ask for text or flag the uncertainty up front.
- Identify the spine. For nonfiction: the central thesis and the 3–7 big ideas that support it. For fiction: premise, central conflict, themes, and arc (respecting spoiler preference). See
references/summary-structures.md. - Summarize at the requested depth:
- One-liner: the single core message in a sentence.
- Executive (~1 page): thesis + key ideas + why it matters.
- Takeaways: a ranked, actionable bullet list.
- Chapter-by-chapter: 2–4 lines per chapter capturing each one's point.
- Keep the best evidence. Preserve the one or two examples, studies, or scenes that make each idea stick — concrete beats abstract.
- Add actionable takeaways (for nonfiction): what to do differently, as concrete steps.
- Stay faithful + neutral. Represent the author's argument accurately before adding any critique. Separate "what the book says" from "my take." Flag where the book is contested if relevant.
- (Optional) discussion/study layer. Book-club questions, key terms, or quiz prompts on request.
What ships with it
2 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.
- 1mo ago First seen · 64 lines · 112 tokens per session scan A 3a32f6304206
book-summarizer is a skill published in the GitHub repository JayRHa/AgentSkills (12 stars, last pushed 2mo ago), licensed MIT. It adds 112 tokens to every session and 1,064 once invoked, about $0.0004 per session on Opus 5.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 skills, from other repositories
code-explainer
Paste any code snippet and get a plain English explanation of what it does and how it works.
ailmanac
Use when the user asks how to do something with Claude, Claude Code, the Claude API, MCP, agents or prompting, or how AI models and tools compare — features, flags, settings, limits, costs, best practices, troubleshooting. Looks the answer up in AILmanac, an open field guide whose pages carry "last verified" dates…
student-learning
Use when the user wants to learn or study a topic, understand a concept, prepare for an exam, or be tutored. Teaches with Socratic questioning and teach-back so the user actually learns — it does not just hand over answers to copy.
canvas
Fetch Canvas LMS courses and assignments via API token.
rwkv-architecture
RNN+Transformer hybrid with O(n) inference. Linear time, infinite context, no KV cache. Train like GPT (parallel), infer like RNN (sequential). Linux Foundation AI project. Production at Windows, Office, NeMo. RWKV-7 (March 2025). Models up to 14B parameters.
build-interactive-explainers
A guide for building interactive explainers, calculators, and simulations driven by an executable model. Users change inputs, steps, states, or events to understand a rule or see how a process develops over time.