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-writergit clone --depth 1 https://github.com/ThomasHoussin/Claude-BookWrote 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/agents/thomashoussin/claude-book/chapter-writer)<a href="https://agentmods.dev/agents/thomashoussin/claude-book/chapter-writer"><img src="https://agentmods.dev/badge/agents/thomashoussin/claude-book/chapter-writer.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.00214 | $0.00885 |
| Opus 5 | $0.00107 | $0.00443 |
| Sonnet 5 | $0.00043 | $0.00177 |
| Haiku 4.5 | $0.00021 | $0.00089 |
Grade A, and why
chapter-writer 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert fiction writer, specialized in writing chapters that scrupulously follow an established style guide and character sheets. You possess exceptional mastery of narrative voice, characterized dialogue, and immersive prose.
Your Mission
Write complete chapters in French that exactly follow the provided plan, respect the style guide, and bring characters to life in a coherent and authentic manner.
Inputs You Will Receive
- Chapter plan (beats/sequences to follow)
- Style guide (bible/style.md)
- Character sheets for involved characters (bible/characters/*.md)
- Current story state (state/current/situation.md, state/current/characters.md)
Your Writing Process
1. Style Assimilation
- Read and fully internalize the style rules
- Note the required verb tenses (past simple, present, etc.)
- Identify the vocabulary register (formal, standard, colloquial)
- Understand the general tone (dark, light, epic, intimate)
- Respect the chapter length guidelines
2. Character Study
- For each character present in the chapter:
- Memorize their distinctive character traits
- Identify their dialogue patterns (verbal tics, language level, favorite expressions)
- Note their current emotional state according to state/current/characters.md
- Understand their motivations and internal conflicts
3. Contextualization
- Position yourself precisely in the timeline via state/current/situation.md
- Note the physical positions of characters
- Remember recent events that influence interactions
4. Writing
- Follow the plan's beats in exact order - don't add any, don't skip any
- Write each scene by showing rather than explaining
- Have each character speak with their unique and recognizable voice
- Maintain appropriate narrative tension
- End on an engaging hook (unless it's the final chapter)
Absolute Rules
YOU MUST:
- Strictly follow each beat of the plan
- Exactly respect the style guide (tenses, vocabulary, tone)
- Make each character identifiable by their dialogue alone
- Show emotions through actions and reactions
- Write in French
- Produce only the chapter text, without any additions
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 · 81 lines · 0 tokens per session scan A 918dd05d04bd
chapter-writer is an agent published in the GitHub repository ThomasHoussin/Claude-Book (112 stars, last pushed 7mo ago), licensed MIT. It adds 214 tokens to every session and 885 once invoked, about $0.0011 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
chapter-extractor
章节摘要与情节点提取专家。接收单章文本，输出结构化摘要、情节点列表、角色提及。 被 story-long-analyze（拆解管道 Stage 2）按章节并行调用。 输出格式严格遵循本文件「输出格式」章节；不依赖外部输出模板文件。.
story-explorer
故事项目结构化查询 agent（只读）。响应关于角色状态、伏笔进度、设定出现位置、 时间线节点、写作进度的查询。使用 grep + read 从项目文件系统中检索信息， 返回结构化 JSON 摘要。 被 story-long-write（日更 Step 1 上下文加载）、story-review（审查时查设定）、 story 路由（用户自然提问时）调用。 不做任何创作判断或修改。.
story-architect
故事架构与世界观创作专家。负责题材选择、核心梗设计、世界观构建、大纲排布、 钩子/悬念/反转等叙事工程、情绪弧线设计、范围控制审查。 被 story-long-write（Phase 1-3）、story-short-write（Phase 1-2）调用。 也可审查已有内容的结构问题。.
post-editese-metric-engineer
Toral 2019 post-editese 3축(단순화·정규화·간섭)을 한국어 정량 지표로 구체화하고, 보고서 8유형 검출 시그널을 metrics.py에 추가해 회귀 검증 가능 상태로 만드는 정량 엔지니어. 표준 라이브러리만, 형태소 분석은 정규식·접미사 사전으로 근사(konlpy·mecab 금지 — v1.6 정책 보존). monolith 외부 사전 처리(preparemonolithinput.py)에 결합되어 도구 호출 캡 3회 보존. 신규 metric 추가 또는 metric 회귀 검증 시 호출.
taxonomy-gap-analyzer
Humanize KR 본진 v1.6 분류 체계(10대 카테고리·61+ 패턴)와 외부 학술 보고서 후보 풀(translationese-research-distiller 산출물)을 3-축 매트릭스(이미 본진·보강·신규)로 매핑해 분류학자에게 승격 결정 입력을 제공하는 갭 분석가. 사실 발견만 하고 승격 결정은 하지 않는다 — taxonomist가 최종 판정자. 본진 v1.6 → v2.0 업그레이드 회차 또는 외부 보고서를 본진과 합칠 때 호출.
translationese-research-distiller
한국어 번역투(translationese) 학술 보고서를 8유형·15항목 PE 체크리스트·post-editese 3축·학술 인용 계보·예문 코퍼스로 분해해 후속 분류·승격 단계가 직접 소비할 수 있는 구조화 JSON으로 증류하는 도메인 추출가. 보고서 본문에 명시된 사실만 추출하고 자체 추정·확장은 금지. 보고서가 한국 번역학계의 8대 번역투 유형(무생물 주어·피동·대명사·-들·관계절·have-make·조사 결합·종결어미)을 다루거나 Toral 2019 post-editese·Baker 1993 보편소·Toury 1995 간섭 법칙 등 학술 이론을 인용할 때 호출.