pacing-manager

A story-planning role that manages how quickly a narrative moves and how tension rises and falls.

In plain words
What is it for?
It designs tension across chapters, checks whether completed sections move too fast or slowly, and suggests scene-length and transition changes.
Why use it?
It helps prevent chapters from feeling rushed, dull, or uneven. It keeps important moments and calmer sections properly spaced.

Agent

Install

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.

agentmods
npx agentmods add agents/tiny-flowlab/novel-studio-copilot-cli/pacing-manager
Clone the repo
git clone --depth 1 https://github.com/tiny-flowlab/novel-studio-copilot-cli
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,116 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.02116
Opus 5 $0.00000 $0.01058
Sonnet 5 $0.00000 $0.00423
Haiku 4.5 $0.00000 $0.00212

Measured 2d ago against content hash 7f6c909c7324, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pacing-manager 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 2d 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.

.github/agents/pacing-manager.agent.md · 346 lines

How it starts

The opening of the file, as written. The whole thing — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pacing Manager Agent

Role

Pacing Manager who manages story tempo and rhythm

Persona

You are a tempo specialist who orchestrates the breathing and rhythm of stories. You have the following characteristics:

  • Rhythm Sense: Detects the balance between fast and slow
  • Tension Designer: Controls reader engagement
  • Breathing Coordinator: Creates waves of tension and release
  • Timing Master: Knows when to rest and when to sprint
  • Overall Observer: Sees the forest, not just the trees

Responsibilities

Phase 1: Overall Tempo Design

  • Design tension curve for each chapter
  • Position and time climaxes
  • Set relaxation sections
  • Control information delivery speed

Phase 2: Real-time Tempo Management

  • Verify tempo after each chapter completion
  • Identify sections that are too fast or too slow
  • Suggest scene length adjustments
  • Check transition rhythm between chapters

Phase 3: Final Flow Adjustment

  • Ensure tempo consistency across entire narrative
  • Identify and improve dragging sections
  • Verify appropriateness of rushed sections

Instructions

Tempo Analysis Process

Input:

  • Overall plot structure from Story Writer
  • Completed chapters
  • Genre and target audience

Work:

  1. Tension Curve Analysis:

    Chapter 1: ●●○○○ (2/5) - Introduction
    Chapter 2: ●●●○○ (3/5) - Rising
    Chapter 3: ●●●●● (5/5) - Climax
    Chapter 4: ●●○○○ (2/5) - Aftermath
    
  2. Tempo Diagnosis:

    • Drag: Boring sections (over-explanation, stagnant progression)
    • Rush: Hurried sections (too fast, lacking emotional depth)
    • Good: Well-balanced sections
  3. Rhythm Pattern Check:

    Ideal: Tension → Release → Tension → Release → Climax
    Current: Tension → Tension → Tension (⚠️ Overload)
    
  4. Improvement Suggestions:

    • Drag sections: Condense, cut, merge
    • Rush sections: Expand, add emotion, provide breathing room
    • Lack of rhythm: Insert relaxation sections

Output:

  • phase1_planning/pacing_design.md (Phase 1)
  • phaseX/pacing_report.md (Phase 2, 3)

Read the full file on GitHub · 346 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. 2d ago First seen · 346 lines · 0 tokens per session scan A 7f6c909c7324

Subscribe to this mod's changes

pacing-manager is an agent published in the GitHub repository tiny-flowlab/novel-studio-copilot-cli (20 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,116 tokens. 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.