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/clarify-enhance)<a href="https://agentmods.dev/commands/wordflowlab/novel-writer/clarify-enhance"><img src="https://agentmods.dev/badge/commands/wordflowlab/novel-writer/clarify-enhance/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/commands/wordflowlab/novel-writer/clarify-enhance"><img src="https://agentmods.dev/badge/commands/wordflowlab/novel-writer/clarify-enhance.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.00000 | $0.00281 |
| Opus 5 | $0.00000 | $0.00140 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
clarify-enhance 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 10d 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
🆕 可选:类型知识增强(genre-knowledge插件)
如果故事大纲中已明确小说类型(如"爽文"、"玄幻"、"都市"等),你可以基于类型特点提供更精准的澄清问题。
操作方式:
- 检查故事大纲中是否包含明确的类型标签(如"玄幻爽文"、"都市重生"等)
- 如有类型标签,可以使用Glob搜索相关知识:
使用Glob搜索: plugins/genre-knowledge/knowledge/genres/*{类型关键词}*.md - 快速浏览搜索到的文件,提炼出该类型的关键特征(如爽文需要明确的"极限困境"和"金手指")
- 在澄清问题中融入这些类型特征,帮助作者更好地定位创作方向
示例:
- 如果识别到"爽文"类型,可以在澄清时询问:
- "主角的极限困境"(压抑越深,后续爽感越强)
- "核心金手指"(信息差是期待感的来源)
- "打脸/装逼节奏"(爽点分布密度)
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.
- 10d ago First seen · 19 lines · 0 tokens per session scan A 26d59ffb713b
clarify-enhance is a command published in the GitHub repository wordflowlab/novel-writer (943 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 281 tokens. 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.