Borrowing it
Nothing to install: this file belongs to nicograef/handbook. 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/nicograef/handbook/main/.claude/skills/audiobook/SKILL.mdgit clone --depth 1 https://github.com/nicograef/handbookWrote 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/nicograef/handbook/audiobook)<a href="https://agentmods.dev/skills/nicograef/handbook/audiobook"><img src="https://agentmods.dev/badge/skills/nicograef/handbook/audiobook.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.00072 | $0.01759 |
| Opus 5 | $0.00036 | $0.00879 |
| Sonnet 5 | $0.00014 | $0.00352 |
| Haiku 4.5 | $0.00007 | $0.00176 |
Grade A, and why
audiobook 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audiobook subject: $ARGUMENTS
Never write chapters before step 7 is complete. Research and structure first.
- Pipeline and rendering: guides/audiobook-pipeline.md
- Prose rules for the ear: listenability.md
- German prose, English terms: german-narration.md
- Review contracts: review-rounds.md
Workflow
Understand
- Draft the scope. Derive it from the argument and the repository.
- A whole-repo subject narrows to the subsystem carrying the most concepts.
- Length is never a scoping input.
- Inventory. Read the code and docs that touch the subject.
- List every concept in play, each with the file where it lives.
- Record decisions the code makes silently. They become chapter hooks.
- Name the gaps. State what the docs assume but never explain.
- This gap is the book. Anything already documented is filler.
- Separate three kinds: missing theory, undocumented decision, open question.
Confirm
- The one checkpoint. Ask before the first expensive step, never after.
- Earlier the proposal would be a guess, with no inventory behind it.
- Later the research is already paid for, and a wrong scope wastes all of it.
- Research is the first expensive step. The checkpoint guards exactly that line.
- Three items only: scope boundary, guiding questions, prior knowledge.
- Offer prior-knowledge levels the user can pick without thinking.
- For example: new to the domain; working knowledge but no theory; solid theory, only this system is new.
- Propose a concrete default for all three items. Never ask an open question.
- A bare "ja" must be a complete, valid answer that starts the run.
- Present the scope as in-scope and out-of-scope, both named explicitly.
- List the guiding questions as the questions the book will answer.
- Ask all three in one interaction. Never split them across turns.
- Never ask about what is derived, not decided:
What ships with it
3 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.
- 3d ago Changed · -3 lines c52bb4d77bf5
- 7d ago First seen · 145 lines · 72 tokens per session scan A 8863f3b83add
audiobook is a skill published in the GitHub repository nicograef/handbook (2 stars, last pushed 4d ago), licensed MIT. It adds 72 tokens to every session and 1,759 once invoked, about $0.0004 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 skills, from other repositories
baoyu-comic
A creator for educational comics, including biographies and tutorials, that turns supplied content or topics into illustrated comic pages.
html-ppt-zhangzara-cartesian
An economics senior thesis on the employment effects of local minimum-wage increases — identification strategy, evidence, and limitations. Built as a decision-grade coursework defense deck for thesis committee.
html-ppt-zhangzara-daisy-days
A customer-success workshop onboarding users to a project-management app — the first-value path and the habits that retain. Built as a decision-grade professional training deck for new customers, CS team.
html-ppt-zhangzara-playful
A retail sales-floor training on consultative selling — the flow, the role-plays, and the daily habit that lifts conversion. Built as a decision-grade professional training deck for store associates, floor managers.
html-ppt-zhangzara-retro-windows
An IT security-awareness training on spotting phishing — the tells, the drill, and what to do in the first 60 seconds. Built as a decision-grade professional training deck for all employees.
sprite-animation
A pixel / sprite-style animated explainer slide — full-bleed cream stage, bold display year, animated pixel-art mascot (e.g. Hanafuda card, mushroom, or 8-bit console), kinetic Japanese display type, ticking timeline ribbon. Reads like a single frame of an educational motion video — looping CSS keyframes, no JS, ready…