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 robertguss/claude-code-toolkit --skill ebook-concept-developmentgit 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/ebook-concept-development)<a href="https://agentmods.dev/skills/robertguss/claude-code-toolkit/ebook-concept-development"><img src="https://agentmods.dev/badge/skills/robertguss/claude-code-toolkit/ebook-concept-development/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/robertguss/claude-code-toolkit/ebook-concept-development"><img src="https://agentmods.dev/badge/skills/robertguss/claude-code-toolkit/ebook-concept-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 60 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00090 | $0.01664 |
| Opus 5.5 | $0.00036 | $0.00666 |
| Sonnet 5.5 | $0.00018 | $0.00333 |
| Haiku 4.5 | $0.00009 | $0.00166 |
Grade A, and why
ebook-concept-development 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ebook Concept Development
Take ONE ebook idea and develop it into a structured concept ready for architecture.
Core Philosophy
This is genuine intellectual partnership, not facilitated questioning:
- Contribute substance — Offer observations, insights, and ideas proactively. Don't just ask questions; bring thinking to the table.
- Push back with reasoning — Challenge weak ideas, but always explain WHY. "This scope feels too big because..." not just "This scope feels too big."
- One question at a time — Never overwhelm with multiple questions. One focused question per response.
- Surface problems early — Better to kill a weak concept now than finish a weak ebook later.
- Respect the human's judgment — Make your case, provide reasoning, but the human decides.
What Makes This Ebook-Specific
Unlike generic brainstorming, this skill constantly applies ebook-specific pressure:
- Format-fit calibration — Is this genuinely ebook-sized? Too thin = blog post. Too thick = full book.
- Value density thinking — Ebooks are concentrated solutions. Every element must earn its place.
- Transformation sizing — Ebook transformations are tight and specific, not sprawling.
The Five Core Elements
Every ebook concept needs these developed:
| Element | Core Question | "Developed" Means |
|---|---|---|
| Reader | Who specifically is this for? | A specific person, not a category. Their situation, problem, what they've tried. |
| Transformation | Where before → where after? | Concrete states. You can picture the person at each point. |
| Promise | What does the reader get? | One compelling sentence. Specific, believable, would make someone pay. |
| Content Source | What existing content feeds this? | Clear inventory: original creation, repurposed content, extracted from larger work. |
| Scope & Format | What's the shape? | Word count range, format type, platform, what's explicitly OUT. |
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.
- 1mo ago First seen · 217 lines · 90 tokens per session scan A fc7318e0483e
ebook-concept-development is a skill published in the GitHub repository robertguss/claude-code-toolkit (126 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 1,664 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-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-initial-access
Initial access techniques checklist: phishing (spear/smishing), credential stuffing, exposed service exploitation, supply chain attacks, watering hole, VPN/RDP brute force, public-facing application exploitation. Maps to MITRE ATT&CK TA0001. Use when planning initial access phases of red team engagements.
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-container-escape
Container escape and breakout techniques targeting Docker, containerd, and Podman runtimes. Covers privileged container breakout via host filesystem mount and nsenter, Docker socket abuse through /var/run/docker.sock, Linux capability exploitation including CAPSYSADMIN, CAPSYSPTRACE, and CAPNETADMIN, cgroup v1…