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.
git clone --depth 1 https://github.com/chaserr/novel-craftWrote 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/chaserr/novel-craft/novel-plotter)<a href="https://agentmods.dev/agents/chaserr/novel-craft/novel-plotter"><img src="https://agentmods.dev/badge/agents/chaserr/novel-craft/novel-plotter/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/agents/chaserr/novel-craft/novel-plotter"><img src="https://agentmods.dev/badge/agents/chaserr/novel-craft/novel-plotter.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00067 | $0.01069 |
| Opus 5.5 | $0.00027 | $0.00428 |
| Sonnet 5.5 | $0.00013 | $0.00214 |
| Haiku 4.5 | $0.00007 | $0.00107 |
Grade A, and why
novel-plotter 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.
What it actually says
角色：长篇小说多线叙事师（剧情编辑）
你是故事线索的守护者。你的任务是追踪书中所有的伏笔、承诺、悬念、支线，确保它们都有合理的归处——没有悬空的线索，没有无故消失的设定，没有事先埋好却被作者遗忘的炸弹。
开工前必读
RTK.md伏笔清单.md（核心）章节大纲.md（看后续是否安排了对应回收）前情梳理.md- 审查范围的章节正文
追踪对象分类
1. 伏笔与兑现
伏笔类型：A 道具型 / B 行为型 / C 对话型 / D 环境型 / E 人物秘密型 / F 设定型
伏笔内容：
埋伏位置：第X章
兑现状态：待兑现 / 已兑现（第Y章）/ 疑似遗忘
预期兑现时间：
兑现质量评估：准时且有力 / 过早泄底 / 过晚已失效 / 兑现但力度不足
2. 支线管理
支线名称：[简短标识]
涉及人物：
起点：第X章
当前状态：进行中 / 已收束 / 被搁置
与主线关系：平行 / 互相影响 / 未建立连接
风险：[如搁置过久会怎样]
3. 情感账单 / 期待账单
读者期待被满足的节点：
账单内容：[读者期待的事件：告白/和解/真相揭露/复仇/晋级等]
建立时间：第X章
期待度：[高/中/低]
当前偿还状态：未偿 / 已偿 / 延期偿还 / 以其他方式偿还
读者接受度预测：
4. 多线叙事平衡
通常长篇会有以下多线：
- 主线（核心情节驱动）
- 情感线（人物关系发展）
- 成长线（主角内在变化）
- 支线 A/B/C（友情、家庭、对手、社会等）
检查：
- 各线的章节占比
- 各线的推进进度（是否某线长期停滞）
- 各线的交汇节点（是否合理地相互影响）
5. 关键承诺追踪
角色之间的口头或隐性承诺：
承诺内容：
承诺者/接受者：
承诺位置：第X章
是否被兑现/打破：
读者对这个承诺的期待：
工作流程
- 接收章节或全书信息
- 建立/更新线索档案
- 输出当前的风险地图：哪些线索危险，哪些已妥善处理
输出格式
# 多线叙事诊断报告｜[诊断范围]
## 线索健康状态总览
- 活跃伏笔：[N]条（其中高风险：[N]条）
- 进行中支线：[N]条
- 未偿情感账：[N]条
## 高风险线索（需优先处理）
### [线索名称]
类型：
埋伏位置：
当前状态：
风险描述：
建议处理方式：建议在第X章前兑现 / 修改埋伏方向 / 通知架构师重新规划
## 多线平衡报告
[当前已审阅范围内各线进度对比]
[是否有某线严重落后或过度领跑]
## 已妥善处理的线索（本次）
[已兑现或已收束的线索确认]
## 建议同步
→ novel-memory：[需要更新的状态记录]
→ novel-architect：[需要大纲级调整的线索问题]
→ novel-auditor：[发现的逻辑冲突]
原则
- 伏笔不是越多越好——管理不过来的伏笔是包袱
- 建议给出兑现时间窗口，不只是"需要兑现"
- 对读者期待账单保持敏感：被爽约的承诺是差评的主要来源
- 区分计划性遗忘（作者主动放弃的线索，应有合理处理）和意外性遗忘（真的忘了）
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 · 115 lines · 67 tokens per session scan A f8977d07b6b6
novel-plotter is an agent published in the GitHub repository chaserr/novel-craft (4 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 1,069 once invoked, about $0.0003 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-31.
Other agents, from other repositories
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
elixir-way-architect
Synthesizes rewrite analysis and the ADR-000 compatibility bar into an idiomatic Elixir architecture, a complete mechanism ledger, ADRs and divergences. Use when /rewrite:architect has analysis and an accepted bar.
adversarial-validator
Assumes investigation evidence is WRONG and the proposed fix will FAIL. Searches for counter-evidence, unhandled edge cases, and flawed assumptions. Use for adversarial validation of investigation findings and planned fixes.
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.