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 commands/wordflowlab/novel-writer/plot-checkgit clone --depth 1 https://github.com/wordflowlab/novel-writerWrote 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/commands/wordflowlab/novel-writer/plot-check)<a href="https://agentmods.dev/commands/wordflowlab/novel-writer/plot-check"><img src="https://agentmods.dev/badge/commands/wordflowlab/novel-writer/plot-check.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.00014 | $0.00550 |
| Opus 5 | $0.00007 | $0.00275 |
| Sonnet 5 | $0.00003 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
plot-check 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.
What it actually says
检查情节发展
分析当前章节与大纲的对齐情况，验证情节发展的连贯性。
检查内容
- 情节节点对齐 - 验证当前进度与大纲规划是否一致
- 伏笔追踪 - 检查已埋设的伏笔和回收计划
- 冲突发展 - 确认冲突升级符合预期节奏
- 角色成长 - 验证角色发展与规划一致
使用方法
执行脚本 {SCRIPT}，将会：
- 读取
spec/tracking/plot-tracker.json - 对比
outline.md中的规划 - 分析已写章节内容
- 生成一致性报告
输出示例
✅ 情节发展检查报告
━━━━━━━━━━━━━━━━━━━━
📍 当前进度：第61章（第二卷）
📊 对齐状态：与大纲一致
⚠️ 待处理伏笔：
- 青铜古镜的秘密（第2章埋设）
- 东厂的真实目的（第9章埋设）
✓ 已完成节点：
- 科举及第 ✓
- 获得改革传承 ✓
→ 下一个节点：组建改革派系
💡 建议：第65章前需要引入新的冲突点
智能检查功能
-
自动更新当前状态
- 读取最新写作进度
stories/*/progress.json - 更新
plot-tracker.json的 currentState - 同步章节和位置信息
- 读取最新写作进度
-
关联数据检查
- 对比
timeline.json确认时间连续性 - 检查
relationships.json中的冲突是否体现 - 验证
character-state.json中的角色位置
- 对比
-
智能建议
- 根据当前进度提醒即将到来的情节点
- 建议合适的伏笔回收时机
- 提示需要加强的冲突升级
数据同步
检查完成后自动：
- 更新 plot-tracker.json 的检查时间
- 记录发现的问题到 notes 字段
- 生成下一步行动建议
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 · 72 lines · 14 tokens per session scan A 20354744da6c
plot-check is a command published in the GitHub repository wordflowlab/novel-writer (939 stars, last pushed 10mo ago), licensed MIT. It adds 14 tokens to every session and 550 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.