Claude-Book: Agent for Claude Code

.claude/agents/chapter-planner.md

chapter-planner is an agent for Claude Code from ThomasHoussin/Claude-Book. It costs 236 tokens per session (967 once invoked), scanned A, original, MIT.

A planning guide for deciding what should happen in a novel chapter before the chapter is written. It turns the story's current state and larger plan into a sequence of plot and character moments.

In plain words
What is it for?
Use it to plan a specific chapter, including its actions, emotional changes, dramatic progression, and connection to the rest of the story.
Why use it?
Writing without a chapter plan can lead to slow pacing, missing story goals, or events that do not follow logically from earlier chapters. This provides a concrete guide for the writer.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is ThomasHoussin/Claude-Book's own configuration. It tells Claude Code how to work on Claude-Book itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Claude-Book configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ThomasHoussin/Claude-Book. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ThomasHoussin/Claude-Book/main/.claude/agents/chapter-planner.md
Clone the repo
git clone --depth 1 https://github.com/ThomasHoussin/Claude-Book

Made for: Claude Code.

Wrote 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.

agentmods badge for chapter-planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/thomashoussin/claude-book/chapter-planner/github.svg)](https://agentmods.dev/agents/thomashoussin/claude-book/chapter-planner)
Your own site
<a href="https://agentmods.dev/agents/thomashoussin/claude-book/chapter-planner"><img src="https://agentmods.dev/badge/agents/thomashoussin/claude-book/chapter-planner/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.

agentmods 80×15 button for chapter-planner

Your own site · 80×15
<a href="https://agentmods.dev/agents/thomashoussin/claude-book/chapter-planner"><img src="https://agentmods.dev/badge/agents/thomashoussin/claude-book/chapter-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 236 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 967 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00236 $0.00967
Opus 5.5 $0.00094 $0.00387
Sonnet 5.5 $0.00047 $0.00193
Haiku 4.5 $0.00024 $0.00097

Measured 1mo ago against content hash 82f66c9a48c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.claude/agents/chapter-planner.md · 91 lines

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

  1. 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
  2. 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
  3. 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
  4. 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]

Read the full file on GitHub · 91 lines

Changes

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.

  1. 1mo ago First seen · 91 lines · 0 tokens per session scan A 82f66c9a48c1

Subscribe to this mod's changes

chapter-planner is an agent published in the GitHub repository ThomasHoussin/Claude-Book (129 stars, last pushed 9mo ago), licensed MIT. It adds 236 tokens to every session and 967 once invoked, about $0.0009 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.

Related

Other agents, from other repositories

post-editese-metric-engineer

A measurement tool for studying Korean writing patterns linked to post-editese, meaning wording that becomes simplified, standardized, or shaped by English sentence patterns during editing. It adds these measurements and eight detection signals to an existing metrics file.

epoko77-ai/im-not-ai · 158 tokens

translationese-research-distiller

A Korean-language research extraction role that breaks an academic report about translation patterns into structured facts, examples, and editing checklists.

epoko77-ai/im-not-ai · 198 tokens

taxonomy-gap-analyzer

An analysis agent for comparing outside research patterns with an existing Korean AI-writing classification system. It records whether each pattern is already covered, partly covered, or new.

epoko77-ai/im-not-ai · 142 tokens

korean-ai-tell-taxonomist

A specialist agent that maintains a classification system for patterns that can make Korean writing look AI-generated. It reviews observed examples, assigns categories and severity levels, and manages taxonomy versions.

epoko77-ai/im-not-ai · 90 tokens

patina-fidelity-auditor

Triggers to audit whether a patina rewrite preserved meaning versus the original text. Invoke this agent after a rewrite is produced; provide both the ORIGINAL and the REWRITE. It checks all four fidelity criteria from core/scoring.md §§9-14 (claims, fabrication, audience/register, length) and returns a…

devswha/patina · 80 tokens

plan-checker

Reviews a unit plan for completeness and craft soundness before drafting begins. Catches gaps, contradictions, and weak spots.

hannsxpeter/scriveno · 28 tokens