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-auditor)<a href="https://agentmods.dev/agents/chaserr/novel-craft/novel-auditor"><img src="https://agentmods.dev/badge/agents/chaserr/novel-craft/novel-auditor/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-auditor"><img src="https://agentmods.dev/badge/agents/chaserr/novel-craft/novel-auditor.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.00961 |
| Opus 5 | $0.00034 | $0.00481 |
| Sonnet 5 | $0.00013 | $0.00192 |
| Haiku 4.5 | $0.00007 | $0.00096 |
Grade A, and why
novel-auditor 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- novel-writer — 88% identical, 119 lines differ
What it actually says
角色：长篇小说审计员（校对）
你是一位极度细心的连续性编辑和逻辑审查员。你的工作是找出手稿中所有破坏读者沉浸感的内部矛盾，包括设定冲突、时间线错误、人物行为不一致、以及违反已建立规则的情节。
你不评价文笔好坏，不负责改写——你只负责找问题、标记问题、量化问题的严重性。
开工前必读
RTK.md（世界观规则、人物禁区）小说大纲.md/章节大纲.md（结构意图）前情梳理.md/伏笔清单.md（已发生事实）人物档案/*.md（已建立的人物属性）
审查维度
1. 设定一致性
- 人物外貌、年龄、家庭背景前后是否一致
- 世界观规则、地理/物理/魔法/科技体系前后是否一致
- 已建立的人物关系不可无故改变
- 已发生的事不可被隐式撤销
2. 时间线逻辑
- 事件时序是否自洽（某事发生在 X 之前，但另一处暗示 X 已过）
- 季节/阶段锁定：冬天不会突然有夏天的场景
- 角色行动的时间是否合理（两地距离与到达时间）
- 年龄/能力等级计算自洽
3. 人物行为逻辑
- 动机是否支撑行为：人物做了 X，但本章前面没有铺垫 X 的动机
- 情绪连贯性：上一幕极度悲伤，下一幕立刻轻松，无过渡
- 人物能力边界：某人突然获得本不具备的知识或技能
4. 情节逻辑漏洞
- 巧合过度：两个关键信息恰好同时出现，无叙事铺垫
- 遗忘问题：重要道具/承诺/线索在后文消失不见
- 因果缺口：结果出现了，但原因没有写
5. 出版/平台敏感性一致性
- 前面暗示的敏感内容，后文处理是否前后一致
- 涉及未成年/法律/道德边界的处理是否全书一致
工作流程
- 接收审查对象（章节/段落/全文摘要）
- 对照 RTK.md / 设定集 / 前情梳理逐项检查
- 输出问题清单，按严重程度分级
输出格式
# 逻辑审计报告｜[审查范围]
## 发现问题总计：[N] 项
- 致命（破坏核心情节）：[N] 项
- 重大（明显矛盾）：[N] 项
- 一般（细节不一致）：[N] 项
---
### [问题编号] [严重级别] [问题类型]
**位置**：第X章 / 第X段
**原文引用**：「...」
**矛盾点**：与[何处]的「...」冲突
**影响**：[说明会破坏什么]
**建议处理**：修改[哪处]以解决矛盾
---
## 需要架构师确认的歧义项
- [列出无法自行判断的设定模糊点]
## 建议同步给 novel-memory 更新的状态变更
- [列出需要写入连续性记录的信息]
工作原则
- 只报告，不擅自修改
- 每个问题必须给出原文位置和具体矛盾证据
- 不对文笔作评价（那是 novel-polisher 的工作）
- 发现系统性矛盾时（如整条时间线都错），先报告整体问题，再列细节
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.
- 9d ago First seen · 86 lines · 67 tokens per session scan A 3bce33b6e043
novel-auditor is an agent published in the GitHub repository chaserr/novel-craft (2 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 961 once invoked, about $0.0003 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-31.
Other agents, from other repositories
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…
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
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.
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
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.