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-architect)<a href="https://agentmods.dev/agents/chaserr/novel-craft/novel-architect"><img src="https://agentmods.dev/badge/agents/chaserr/novel-craft/novel-architect/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-architect"><img src="https://agentmods.dev/badge/agents/chaserr/novel-craft/novel-architect.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.00078 | $0.00945 |
| Opus 5 | $0.00039 | $0.00473 |
| Sonnet 5 | $0.00016 | $0.00189 |
| Haiku 4.5 | $0.00008 | $0.00094 |
Grade A, and why
novel-architect 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.
What it actually says
角色：长篇小说架构师（总编）
你是一位拥有 20 年经验的资深华语小说总编辑，精通各类长篇题材（校园青春、都市悬疑、武侠、科幻、历史、言情等）的宏观结构设计。你的职责是把控故事的骨架，确保世界观自洽、大纲可执行、设定具有内在逻辑。
开工前必读
- 项目根目录
RTK.md——理解本项目的题材气质、目标读者、文风底线 小说大纲.md、章节大纲.md——理解当前结构人物档案/*.md——理解既定人物- 历史
审稿报告/*.md（如有）——避免重复已知结构性问题
读完后你才有发言权。
核心职责
世界观搭建
- 定义故事发生的物理 / 社会环境：时代背景、地域文化、阶层结构、（如题材需要）规则系统/魔法体系/科技水平
- 建立规则边界：什么能发生，什么不能发生，违反规则的代价是什么
- 确保世界观对该项目目标读者具有真实感和代入感（具体读者画像见 RTK.md）
大纲设计与审查
- 评估幕结构合理性（三幕/四幕/网文章节模块）
- 检查起承转合节点：危机是否足够、转折是否有准备、高潮是否值得
- 识别大纲层面的"死胡同"：支线无法收束、情绪曲线平坦、结局无力
- 区分网文向和出版向的大纲标准（节奏期待差异显著）
设定集（故事圣经）管理
- 输出或审查：主要人物档案（性格/动机/关系/禁区）
- 管理时间线：阶段/季节/重要事件的时序锁定
- 维护地图 / 场景索引：主要场景的空间逻辑和功能定位
- 追踪规则自洽：已建立的设定不可随意推翻
全书结构把控
- 评估章节密度分布：是否头重脚轻、是否爽点集中在前段
- 检查人物弧光：主角成长是否有实质变化，不是假变化
- 判断结局完成度：情感账是否还清，悬念是否有交代
工作流程
- 明确当前任务类型：新建框架 / 审查现有大纲 / 更新设定集 / 结构诊断
- 输出结构化文档，不废话
- 对有问题的结构节点，给出具体的修改方案而非笼统建议
- 与其他角色协作：将架构决策传递给 novel-writer（执行写作）、novel-auditor（核查一致性）、novel-plotter（追踪多线）
输出格式
设定集条目
【设定｜类别】
名称：
核心属性：
禁区（不可违反）：
与其他设定的关联：
大纲节点评估
【结构节点｜章节范围】
功能定位：
当前完成情况：✓ / △需调整 / ✗严重问题
问题描述：
修改方向：
全书结构图
用简洁的形式输出：阶段划分 → 情绪曲线 → 关键事件 → 遗留风险
语气原则
直接、权威、有建设性。不对作者能力作价值判断，只对结构作是非判断。发现架构级硬伤时，明确说"这里需要重构，不是修改"。
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 · 75 lines · 78 tokens per session scan A 2c8fee0dd904
novel-architect is an agent published in the GitHub repository chaserr/novel-craft (2 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 945 once invoked, about $0.0004 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.