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/robertguss/claude-code-toolkit/book-ideationnpx skills add robertguss/claude-code-toolkit --skill book-ideationgit clone --depth 1 https://github.com/robertguss/claude-code-toolkitWrote 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/robertguss/claude-code-toolkit/book-ideation)<a href="https://agentmods.dev/skills/robertguss/claude-code-toolkit/book-ideation"><img src="https://agentmods.dev/badge/skills/robertguss/claude-code-toolkit/book-ideation.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.00092 | $0.01727 |
| Opus 5 | $0.00046 | $0.00864 |
| Sonnet 5 | $0.00018 | $0.00345 |
| Haiku 4.5 | $0.00009 | $0.00173 |
Grade A, and why
book-ideation 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Book Ideation
Transform raw ideas into structured nonfiction book concepts through guided multi-session development.
Core Philosophy
Every decision serves the reader. The question is never "what do I want to say?" but "what transformation does the reader need, and how can this book deliver it?"
This skill sits between generic brainstorming and book architecture. Its job is to refine raw material into a structured concept that can be validated, market-tested, and architected.
The goal is not a book outline. The goal is clarity on eight fundamental elements that determine whether a book should exist and what it must accomplish.
Input Types
This skill accepts:
- Raw idea (one sentence or paragraph)
- Brainstorm document from the
brainstormskill - Zettelkasten notes or research collection
- Existing partial concept needing refinement
- "Shower thought" worth exploring
Session Flow
Session Start
Begin every session with:
-
New or continuing?
- If continuing: Request the latest Book Concept Document version
- If new: Proceed to initialization
-
What do we have?
- Ask user to share their raw material (brainstorm doc, notes, idea)
- Read and identify what's already clear vs. underdeveloped
-
Session goal
- Which elements need development today?
- Deep exploration or quick progress?
The Eight Elements
Develop these through conversation, not interrogation. Surface insights; don't extract data.
1. The Reader
Who specifically is this for?
Go beyond demographics. Understand:
- Their current situation (what's happening in their life/work)
- What they currently believe that isn't serving them
- What they've already tried that hasn't worked
- What's blocking them from solving this themselves
- Why they would pick up THIS book (the trigger moment)
Probe: "If your ideal reader walked into a bookstore, what section would they be in? What would they be feeling? What search would they have just done on Amazon?"
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.
- 4d ago First seen · 248 lines · 92 tokens per session scan A ec4fbfdea0d0
book-ideation is a skill published in the GitHub repository robertguss/claude-code-toolkit (108 stars, last pushed 26d ago), licensed MIT. It adds 92 tokens to every session and 1,727 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
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
offensive-edr-evasion
EDR evasion offensive checklist: hook unhooking (user/kernel), direct syscalls, PPID spoofing, process injection variants, AMSI bypass, ETW patching, memory encryption, and behavior-based evasion. Use when planning EDR bypass during red team engagements or researching AV/EDR evasion techniques.
offensive-mitigations
Security mitigation reference and bypass catalog: ASLR, DEP/NX, RELRO, stack canaries, CFI, sandboxing, seccomp. Covers both detection of enabled mitigations and known bypass techniques. Use when assessing target hardening or planning exploit mitigation bypasses.
offensive-exploit-development
Exploit development operational guide: environment setup, debugging workflow, PoC development lifecycle, writing reliable exploits, using pwntools/pwndbg, heap exploitation techniques, and weaponization considerations. Use when actively developing exploits or setting up an exploit dev environment.
offensive-tls-attacks
Comprehensive methodology for auditing and exploiting TLS/SSL implementations and misconfigurations across network services and mobile applications. Covers protocol downgrade attacks including POODLE (CVE-2014-3566) against SSLv3 CBC padding, DROWN (CVE-2016-0800) cross-protocol attack leveraging SSLv2 export ciphers…
offensive-advanced-redteam
Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…