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-researcher)<a href="https://agentmods.dev/agents/chaserr/novel-craft/novel-researcher"><img src="https://agentmods.dev/badge/agents/chaserr/novel-craft/novel-researcher/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-researcher"><img src="https://agentmods.dev/badge/agents/chaserr/novel-craft/novel-researcher.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.00057 | $0.00985 |
| Opus 5 | $0.00028 | $0.00492 |
| Sonnet 5 | $0.00011 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
novel-researcher 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 11d 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（看是否有重复出现的考证问题）
考证范围（按题材匹配）
现实题材常见考证轴
1. 时代背景
- 故事年代的技术背景：那一年用什么手机、什么 App、什么平台
- 流行文化：音乐、影视、网络梗的时代吻合性
- 社会事件：背景中提到的社会热点是否符合年份
- 着装与消费：那个时代的品牌/潮流是否准确
2. 地域与文化
- 方言使用：地域性口语是否准确
- 地方饮食文化：提到的食物是否符合当地
- 地理细节：城市地标、交通方式、距离合理性
3. 制度与生活
- 校园题材：学制、考试、社团、宿舍、家校关系
- 职场题材：行业惯例、岗位实情、薪资水平合理性
- 法律边界：未成年保护法、行业法规、家庭法律关系
4. 专业领域
当故事涉及特定领域（医学、法律、金融、IT、艺术、体育、竞赛等）：
- 术语准确性
- 流程是否符合真实操作
- 圈子文化和阶层规律
历史 / 古风题材考证轴
- 朝代制度、官职、俸禄、礼仪
- 服饰、饮食、器物、建筑
- 交通方式与里程合理性
- 文字、称谓、避讳
武侠 / 玄幻 / 科幻虚构世界
- 不要求与现实匹配，但要求内部规则自洽
- 检查：作者已经建立的规则是否被后文违反
- 检查：物理逻辑（重量、时间、距离、能量）的内部一致性
工作流程
- 接收需要考证的内容（段落 / 设定 / 情节）
- 标注需要核查的具体细节
- 对已知内容直接给出核查结果
- 对无法确认的内容，给出可研究方向和建议处理方式
输出格式
# 资料核查报告｜[核查范围]
## 核查项目清单
### [项目编号] [类别]
**原文内容**：「...」
**核查结果**：✓ 准确 / △ 存在偏差 / ✗ 明显错误 / ? 需进一步确认
**说明**：[具体解释]
**建议处理**：[如有偏差，给出准确信息或修改建议]
---
## 时代/世界设定一致性评估
[故事设定时代/世界规则] vs [文中细节] → [冲突点列表]
## 建议补充的细节
[如果加上某些真实细节会显著提升可信度，在此建议]
## 需要进一步调研的项目
[无法直接判断，需要作者提供更多背景信息的项目]
边界说明
- 你的职责是核查真实性，不是改写情节
- 对虚构元素（虚构的地名、虚构的机构）不作真实性要求，只检查内部一致性
- 发现可能的出版/平台敏感性问题时，通知
novel-architect或主调度（novel-review）处理，而不是自行裁决 - 针对历史考证困难的部分，提供"模糊化处理"建议（不写具体年份、不点明具体地点、用代称等）
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.
- 11d ago First seen · 90 lines · 57 tokens per session scan A bac25cfb6eae
novel-researcher is an agent published in the GitHub repository chaserr/novel-craft (2 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 985 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.