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/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/analyze)<a href="https://agentmods.dev/commands/wordflowlab/novel-writer/analyze"><img src="https://agentmods.dev/badge/commands/wordflowlab/novel-writer/analyze.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.1 | $0.00007 | $0.01824 |
| Opus 5 | $0.00003 | $0.00912 |
| Sonnet 5 | $0.00001 | $0.00365 |
| Haiku 4.5 | $0.00001 | $0.00182 |
Grade A, and why
analyze 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 8d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
对已完成的故事内容进行综合分析，验证是否符合宪法、规格和计划。
目标
像代码审查一样对作品进行全面验证，确保质量和一致性。
执行步骤
1. 加载验证基准
运行 {SCRIPT} 加载所有验证基准文档：
- 宪法文件：
memory/novel-constitution.md - 规格文件：
stories/*/specification.md - 计划文件：
stories/*/creative-plan.md - 任务列表：
stories/*/tasks.md - 已完成内容：
stories/*/content/*.md
2. 宪法合规性检查
验证作品是否遵循创作宪法的原则：
## 宪法合规性报告
### 核心价值观检查
- [ ] 原则1：[检查结果]
- [ ] 原则2：[检查结果]
- [ ] 原则3：[检查结果]
### 质量标准验证
- [ ] 逻辑一致性：[通过/警告/失败]
- [ ] 人物饱满度：[评分]
- [ ] 文字水准：[评分]
### 风格一致性
- [ ] 叙事风格：[一致/偏差]
- [ ] 语言风格：[一致/偏差]
- [ ] 节奏控制：[一致/偏差]
3. 规格符合度分析
检查实现是否满足规格要求：
## 规格符合度分析
### 核心需求覆盖
#### P0（必须包含）
- [需求1]：✅ 已实现
- [需求2]：⚠️ 部分实现
- [需求3]：❌ 未实现
#### P1（应该包含）
[覆盖率：X%]
#### P2（可以包含）
[覆盖率：X%]
### 目标达成度
- 目标读者适配：[X%]
- 市场定位符合：[X%]
- 成功标准达成：[X/Y]
### 约束条件遵守
- 内容红线：✅ 无违规
- 创作约束：✅ 符合要求
- 技术约束：⚠️ [具体问题]
4. 计划执行分析
评估实际执行与计划的偏差：
## 计划执行分析
### 章节架构对比
| 计划 | 实际 | 偏差分析 |
|------|------|----------|
| 第1章：开篇钩子 | ✅ 完成 | 符合预期 |
| 第2章：冲突展开 | ✅ 完成 | 略有调整 |
| 第3章：转折点 | ⚠️ 进行中 | 延后1章 |
### 人物发展轨迹
- 主角成长弧：[符合度X%]
- 配角功能：[实现度X%]
- 关系演变：[符合度X%]
### 世界观展开
- 第一层设定：✅ 按计划展开
- 第二层设定：⚠️ 提前揭示
- 第三层设定：[未到达]
5. 内容质量分析
深入分析作品质量：
## 内容质量分析
### 文本统计
- 总字数：[X]字
- 平均章节长度：[X]字
- 完成进度：[X%]
### 结构分析
- 情节密度：[高/中/低]
- 冲突频率：[X次/章]
- 节奏变化：[图表]
### 技术问题
#### 逻辑问题
1. [位置]：[问题描述]
2. [位置]：[问题描述]
#### 连贯性问题
1. [位置]：[问题描述]
#### 人物一致性
1. [角色]：[行为矛盾点]
### 亮点识别
1. [位置]：[优秀之处]
2. [位置]：[创新点]
6. 任务完成度审计
检查任务执行情况：
## 任务完成度
### 总体进度
- 总任务数：[X]
- 已完成：[Y]
- 进行中：[Z]
- 未开始：[W]
### 关键里程碑
- [里程碑1]：✅ 达成
- [里程碑2]：⚠️ 延期
- [里程碑3]：[待定]
### 阻塞和风险
1. [阻塞项]：[影响分析]
2. [风险项]：[应对建议]
7. 生成改进建议
基于分析结果提供具体建议：
## 改进建议
### 紧急修复（P0）
1. **[问题]**
- 影响：[影响描述]
- 建议：[具体修复方案]
- 位置：[具体章节/段落]
### 优化建议（P1）
1. **[优化项]**
- 当前：[现状]
- 建议：[优化方案]
- 预期效果：[改进效果]
### 长期改进（P2）
1. **[改进方向]**
- 理由：[为什么需要]
- 方案：[如何实施]
- 时机：[何时实施]
8. 生成验证报告
创建 stories/*/analysis-report.md：
# 作品分析报告
## 摘要
- 分析日期：[YYYY-MM-DD]
- 分析版本：[作品版本]
- 总体评分：[X/10]
- 建议行动：[继续/修订/重写]
## 核心指标
| 维度 | 得分 | 说明 |
|------|------|------|
| 宪法合规 | X/10 | [说明] |
| 规格符合 | X/10 | [说明] |
| 计划执行 | X/10 | [说明] |
| 内容质量 | X/10 | [说明] |
| 读者体验 | X/10 | [预估] |
## 关键发现
[3-5个最重要的发现]
## 下一步行动
[基于分析的具体行动建议]
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.
- 8d ago First seen · 273 lines · 7 tokens per session scan A 45b831946330
analyze is a command published in the GitHub repository wordflowlab/novel-writer (940 stars, last pushed 10mo ago), licensed MIT. It adds 7 tokens to every session and 1,824 once invoked, about $0.0000 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
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.
selftest
Validate the lifecycle of an extension from the catalog.
checklist
Generate a custom checklist for the current feature based on user requirements.
specify
Create or update the feature specification from a natural language feature description.
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.