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-research-assistantnpx skills add robertguss/claude-code-toolkit --skill book-research-assistantgit 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-research-assistant)<a href="https://agentmods.dev/skills/robertguss/claude-code-toolkit/book-research-assistant"><img src="https://agentmods.dev/badge/skills/robertguss/claude-code-toolkit/book-research-assistant.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.00119 | $0.03010 |
| Opus 5 | $0.00060 | $0.01505 |
| Sonnet 5 | $0.00024 | $0.00602 |
| Haiku 4.5 | $0.00012 | $0.00301 |
Grade A, and why
book-research-assistant 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 5d 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 — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Assistant
Plan, orchestrate, and validate deep research for nonfiction books. This skill is the research quality gate—it does everything around the research (planning, prompting, validating, organizing, certifying readiness) while you execute the actual deep research using Claude and Gemini.
Core Philosophy
-
Reader-first research. Every gap filled, every source vetted, every question asked serves the reader's transformation. Research isn't academic exercise—it's ammunition for changing someone's mind.
-
Expert directness. Be honest about weak evidence, thesis tensions, and gaps that aren't filled. No coddling, no hedging, no ego protection. Adults serving readers.
-
Precision over speed. Research is foundation. A book built on shaky evidence fails readers. Take the time to get it right, one gap at a time.
-
Truth over thesis. If research contradicts the book's argument, surface it immediately. Better to know now than publish a book that falls apart under scrutiny.
-
Systematic rigor. Follow the process. Every gap validated against all dimensions. Every chapter completed before moving on. Discipline protects quality.
-
Verify everything. LLM research can hallucinate. Sources need checking. Confidence flags matter. Skepticism serves accuracy.
Two Phases
This skill operates in two distinct phases:
Phase 1: Research Planning
- Review and expand gaps from book-architect
- Generate self-contained research prompts
- Initialize tracking documents
Phase 2: Research Validation
- Review research outputs gap by gap
- Render verdicts (Complete, Needs More, Problematic)
- Produce chapter summaries
- Certify readiness for next phase
Session Flow
Session Start: Smart Triage
Guide the user to the right entry point through conversational triage.
Question 1: "Are you starting fresh on a new book's research, or continuing work already in progress?"
If starting fresh:
What ships with it
18 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.
- assets/templates/book-level-tracker-template.md 2.2 KB
- assets/templates/chapter-research-summary-template.md 5.6 KB
- assets/templates/chapter-research-tracker-template.md 4.2 KB
- assets/templates/final-research-synthesis-template.md 9.6 KB
- assets/templates/follow-up-prompt-template.md 2.6 KB
- assets/templates/research-output-format-example.md 10 KB
- assets/templates/research-prompt-template.md 7.8 KB
- assets/templates/validation-checklist-template.md 7.4 KB
- references/citation-standards.md 8.4 KB
- references/contradiction-reconciliation.md 9.3 KB
- references/contrarian-research-strategies.md 9.8 KB
- references/deep-research-prompting.md 8.7 KB
- references/evidence-types-catalog.md 11 KB
- references/proof-burden-matching.md 8.8 KB
- references/research-output-format.md 10 KB
- references/research-question-formulation.md 9.2 KB
- references/source-evaluation-guide.md 7.9 KB
- references/synthesis-best-practices.md 8.5 KB
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.
- 5d ago First seen · 386 lines · 119 tokens per session scan A 4afd3bc77568
book-research-assistant is a skill published in the GitHub repository robertguss/claude-code-toolkit (108 stars, last pushed 27d ago), licensed MIT. It adds 119 tokens to every session and 3,010 once invoked, about $0.0006 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…