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 chapter-architectgit 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/chapter-architect)<a href="https://agentmods.dev/skills/robertguss/claude-code-toolkit/chapter-architect"><img src="https://agentmods.dev/badge/skills/robertguss/claude-code-toolkit/chapter-architect/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/chapter-architect"><img src="https://agentmods.dev/badge/skills/robertguss/claude-code-toolkit/chapter-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Anti-Refusal · line 97 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00052 | $0.01707 |
| Opus 5.5 | $0.00021 | $0.00683 |
| Sonnet 5.5 | $0.00010 | $0.00341 |
| Haiku 4.5 | $0.00005 | $0.00171 |
Grade A, and why
chapter-architect 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chapter Architect
Transform a chapter's high-level specification (from book-architect) into a beat-level outline that guides drafting while preserving creative freedom.
Core Philosophy
-
Reader-first, always. Every beat exists to move the reader toward the chapter's destination—intellectually and emotionally.
-
Compass, not GPS. The outline points direction and marks waypoints. It does not dictate every turn. The ghostwriter has creative freedom within the structure.
-
Collaborative partnership. Claude contributes ideas, challenges weak thinking, and advocates for what serves the reader. The author has final approval on all decisions.
-
Intent over prescription. Each beat captures why it exists, not just what it contains. This enables intelligent adaptation during drafting.
-
Emotional arc matters. Track not just where the reader is intellectually, but how they feel at each stage of the journey.
Session Flow
This skill is session-flexible. Simple chapters may complete in one session. Complex chapters may need natural pause points with thinking time between.
Session Start
-
Identify context:
- New chapter or continuing a previous session?
- If continuing, request the latest working draft.
-
Gather inputs:
- Architecture Document (chapter specification)
- Research Dossier (chapter's section)
- Book Concept Document (reader, promise, voice)
- Any author notes on this chapter
-
Confirm which chapter we're architecting and surface the key specs:
- Chapter number and working title
- Chapter's job
- Reader entry state
- Reader exit state
- Key concepts to cover
- Bridge from previous / to next chapter
Phase 1: Orient
Review inputs together. Surface any tensions, questions, or issues.
Key questions to explore:
- Is this a standard chapter or special type? (introduction, conclusion,
case-study, etc.)
- If special type, read
references/special-chapter-types.md
- If special type, read
- Is the research sufficient? Any gaps?
- Are there competing ways to approach this chapter?
- What's the emotional shape of this chapter? (tension→release,
confusion→clarity, etc.)
- Reference
references/emotional-arc-patterns.mdas needed
- Reference
What ships with it
7 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 · 214 lines · 52 tokens per session scan A e698c7e78d6d
chapter-architect is a skill published in the GitHub repository robertguss/claude-code-toolkit (126 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 1,707 once invoked, about $0.0002 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…