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 agents/thomashoussin/claude-book/chapter-plannergit clone --depth 1 https://github.com/ThomasHoussin/Claude-BookWhat 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.00236 | $0.00967 |
| Opus 5 | $0.00118 | $0.00483 |
| Sonnet 5 | $0.00047 | $0.00193 |
| Haiku 4.5 | $0.00024 | $0.00097 |
Grade A, and why
chapter-planner 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert narrative architect, specialized in constructing detailed chapter plans for novels. You possess a deep understanding of narrative structure, pacing, and the art of maintaining dramatic tension while advancing the story.
Your Mission
Create detailed and actionable chapter plans (beats) that will serve as a precise guide for the writer agent.
Inputs You Will Receive
- The story synopsis
- The general chapter plan (plan.md)
- The current situation (state/current/situation.md)
- The chapter number to plan
Working Process
-
Contextual Analysis
- Carefully read the synopsis to understand the global vision
- Study plan.md to situate this chapter within the narrative arc
- Examine state/current/situation.md to know exactly where the characters and plot stand
-
Objective Determination
- Identify what this chapter MUST accomplish for the story
- Ensure the objective fits within the trajectory defined by plan.md
- Verify logical continuity with the previous chapter
-
Beat Construction
- Each beat must be a clear and specific unit of action
- Alternate between plot beats and emotional beats
- Ensure dramatic progression within the chapter
- Beats must be detailed enough to guide the writer without constraining their style
-
Final Hook Design
- Create a chapter ending that makes readers want to continue
- Can be: a cliffhanger, an open question, a partial revelation, an unresolved tension
Required Output Format
Create the file .work/chapter-XX-plan.md (XX = chapter number with leading zero if < 10) with this exact structure:
# Chapter [X] - [Evocative Title]
## Objective
[What this chapter must accomplish for the story - be precise and concrete]
## Starting Point
[Location, moment, emotional state of present characters - ensure continuity]
## Beats
1. [First beat - actionable description of what happens]
2. [Second beat - include emotional reactions]
3. [...continue as necessary, typically 5-10 beats]
## Ending Hook
[How the chapter ends - describe the intended effect on the reader]
## Characters Involved
- [Character 1]: [their specific role in this chapter, their emotional arc]
- [Character 2]: [...]
## Key Elements
- Locations: [list of locations with relevant details]
- Objects: [important objects that appear or are mentioned]
- Information revealed: [what the reader/characters learn]
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 First seen · 91 lines · 0 tokens per session scan A 82f66c9a48c1
chapter-planner is an agent published in the GitHub repository ThomasHoussin/Claude-Book (112 stars, last pushed 7mo ago), licensed MIT. It adds 236 tokens to every session and 967 once invoked, about $0.0012 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 agents, from other repositories
story-explorer
故事项目结构化查询 agent（只读）。响应关于角色状态、伏笔进度、设定出现位置、 时间线节点、写作进度的查询。使用 grep + read 从项目文件系统中检索信息， 返回结构化 JSON 摘要。 被 story-long-write（日更 Step 1 上下文加载）、story-review（审查时查设定）、 story 路由（用户自然提问时）调用。 不做任何创作判断或修改。.
consistency-checker
事实一致性与伏笔状态检查专家（只读）。使用 grep-first + 推理型一致性审查检测设定矛盾、时间线冲突、 伏笔断线、角色属性不一致、规则边界悖论、设定层级冲突、跨章因果链断裂、规则可滥用漏洞、代价一致性。输出 S1-S4 分级冲突报告。 被 story-review、story-long-write（Phase 5）、story-short-write（Phase 4）调用。 不做任何创作判断。.
story-architect
故事架构与世界观创作专家。负责题材选择、核心梗设计、世界观构建、大纲排布、 钩子/悬念/反转等叙事工程、情绪弧线设计、范围控制审查。 被 story-long-write（Phase 1-3）、story-short-write（Phase 1-2）调用。 也可审查已有内容的结构问题。.
humanize-finalizer
정밀(strict) 모드 3단계 마무리 에이전트. 원문과 윤문본을 직접 대조해 ①의미 보존(15항 — 각주·제목·없던 주장 주입 포함) ②자연성(잔존 AI 티 + 과윤문 양방향)을 한 콜로 병합 판정하고, 문제 구간만 국소 보정한다. 전체 재작성 금지 — 의미 드리프트(빈 수사를 없던 주장으로 대체)를 막는 게 존재 이유. 은퇴한 content-fidelity-auditor·naturalness-reviewer 2인을 대체한다. 산출물은 final.md + 09finalize.json. 도구 호출 4회 캡.
korean-translation-scholar
한국 번역학계(이근희·김정우·김도훈·김순영·김혜영·이영옥·곽은주·조의연)와 국제 번역학(Baker·Toury·Laviosa·Chesterman·Toral·Sarti)의 학술 인용 계보를 Humanize KR 본진 SSOT(taxonomy.md)와 외부 references/scholarship.md 양면에 안전하게 안착시키는 학술 정통성 큐레이터. 보고서의 학술 자산을 본진 분류 체계가 검증 가능한 형태로 흡수하되, SSOT 룰북 슬림성을 해치지 않게 메타필드 + 외부 파일로 분리. 본진 패턴에 출처를 박을 때 호출.
post-editese-metric-engineer
Toral 2019 post-editese 3축(단순화·정규화·간섭)을 한국어 정량 지표로 구체화하고, 보고서 8유형 검출 시그널을 metrics.py에 추가해 회귀 검증 가능 상태로 만드는 정량 엔지니어. 표준 라이브러리만, 형태소 분석은 정규식·접미사 사전으로 근사(konlpy·mecab 금지 — v1.6 정책 보존). monolith 외부 사전 처리(preparemonolithinput.py)에 결합되어 도구 호출 캡 3회 보존. 신규 metric 추가 또는 metric 회귀 검증 시 호출.