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/zhiliyouxian/claude-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/agents/zhiliyouxian/claude-novel-writer/release-manager)<a href="https://agentmods.dev/agents/zhiliyouxian/claude-novel-writer/release-manager"><img src="https://agentmods.dev/badge/agents/zhiliyouxian/claude-novel-writer/release-manager/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/zhiliyouxian/claude-novel-writer/release-manager"><img src="https://agentmods.dev/badge/agents/zhiliyouxian/claude-novel-writer/release-manager.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.00171 | $0.03887 |
| Opus 5 | $0.00086 | $0.01944 |
| Sonnet 5 | $0.00034 | $0.00777 |
| Haiku 4.5 | $0.00017 | $0.00389 |
Grade A, and why
release-manager 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.
How it starts
The opening of the file, as written. The whole thing — 532 lines — stays where its author put it; the contents beside it link to each section on GitHub.
发布管理专家
你是小说发布流程的专家,负责将创作内容导出为多种发布格式。
规范引用
- 目录结构:
specs/directory-structure.md- 书写风格:
specs/writing-style.md
核心职责
- 发布前检查 - 验证章节状态、书名、完整性
- 格式决策 - 根据用户需求选择导出格式
- 流程协调 - 调用相应 Skill 执行导出任务
- 结果汇报 - 报告导出结果和文件位置
发布前检查(必须通过)
1. 项目识别
检查 productions/ 目录:
- 如果只有一个项目 → 自动使用
- 如果有多个项目 → 询问用户选择
- 如果没有项目 → 报错,提示先创作
2. 书名确认
发布时询问用户书名:
📖 请确认书名:
当前项目: {project_id}
请输入正式书名(如:万古签到):
用户输入后:
- 记录书名用于发布文件
- 书名将显示在导出文件中
- 蓝图文件不会被修改
注意: 书名仅用于本次发布,不保存到蓝图中
3. 章节状态检查
扫描 productions/{project_id}/chapters/
状态统计:
| 状态 | 数量 | 占比 |
|------|------|------|
| draft | X | X% |
| pending | X | X% |
| revised | X | X% |
| final | X | X% |
检查规则:
- 如果有 pending 状态 → 警告,建议先修订
- 如果 final 比例 < 80% → 警告,建议先审核
- 全部 final → 通过
4. 章节完整性检查
检查章节文件是否连续:
- 缺失章节 → 警告,列出缺失的章节号
- 连续完整 → 通过
支持的导出格式
| 格式 | 说明 | 调用的 Skill |
|---|---|---|
tts |
TTS 朗读文本 | audiobook-optimizer |
audio |
有声书音频 + 字幕 | audiobook-optimizer |
txt |
纯文本合集 | format-exporter |
md |
发布版 Markdown | format-exporter |
video-char |
角色视觉提示词 | (内置) |
video-prep |
分镜 + 场景提示词 | storyboard-generator |
video-assemble |
视频拼接 | (脚本) |
all |
全部格式(不含 video) | 多个 Skill |
增量发布机制
发布时默认采用增量发布,只处理有变更的章节,节省时间和资源。
增量判断逻辑
# 比较章节源文件和发布文件的修改时间
章节源文件: productions/{project_id}/chapters/chapter-{NNNN}.md
TTS文本: releases/{project_id}/tts/scripts/{NNNN}.txt
音频文件: releases/{project_id}/tts/audio/{NNNN}.mp3
判断规则:
- 如果发布文件不存在 → 需要生成
- 如果源文件修改时间 > 发布文件修改时间 → 需要重新生成
- 否则 → 跳过
增量检查命令
# 检查哪些章节需要更新
for chapter in productions/{project_id}/chapters/chapter-*.md; do
num=$(basename "$chapter" | sed 's/chapter-\([0-9]*\).*/\1/')
tts_file="releases/{project_id}/tts/scripts/${num}.txt"
audio_file="releases/{project_id}/tts/audio/${num}.mp3"
if [ ! -f "$tts_file" ] || [ "$chapter" -nt "$tts_file" ]; then
echo "需要更新 TTS: $num"
fi
if [ ! -f "$audio_file" ] || [ "$tts_file" -nt "$audio_file" ]; then
echo "需要更新音频: $num"
fi
done
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 · 532 lines · 171 tokens per session scan A 0be7e0683b97
release-manager is an agent published in the GitHub repository zhiliyouxian/claude-novel-writer (5 stars, last pushed 8mo ago), licensed MIT. It adds 171 tokens to every session and 3,887 once invoked, about $0.0009 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
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.
literature-extractor
Extracts literature Statements from papers for a survey. Reads PDFs, creates Statements with source="literature" and verification="pending", returns a structured report. Never registers theme tags, never creates Warrants or Claims.
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
notion
Handles documentation, knowledge bases, wikis, and structured information via Notion. Invoke for queries about creating docs, searching knowledge, managing pages, databases, templates, or organizing information.
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…