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/timeline)<a href="https://agentmods.dev/commands/wordflowlab/novel-writer/timeline"><img src="https://agentmods.dev/badge/commands/wordflowlab/novel-writer/timeline/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/timeline"><img src="https://agentmods.dev/badge/commands/wordflowlab/novel-writer/timeline.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.00008 | $0.00393 |
| Opus 5 | $0.00004 | $0.00197 |
| Sonnet 5 | $0.00002 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
timeline 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
时间线管理
维护故事的时间轴，确保时间逻辑的一致性。
功能
- 时间记录 - 追踪每个章节的时间点
- 并行事件 - 管理同时发生的多线剧情
- 历史对照 - 与真实历史事件对比（历史小说）
- 逻辑验证 - 检查时间跨度的合理性
使用方法
执行脚本 {SCRIPT}，支持以下操作：
add- 添加时间节点check- 验证时间连续性show- 显示时间线概览sync- 同步并行事件
时间线数据
时间线信息存储在 spec/tracking/timeline.json 中：
- 故事内时间（年/月/日）
- 章节对应关系
- 重要事件标记
- 时间跨度计算
示例输出
📅 故事时间线
━━━━━━━━━━━━━━━━━━━━
当前时间：万历三十年春
第1章 | 万历二十九年冬月 | 穿越事件
第4章 | 万历三十年正月 | 北上赴考
第6章 | 万历三十年二月 | 会试
第8章 | 万历三十年三月 | 殿试
第61章 | 万历三十年四月 | [待写]
⏱️ 时间跨度：5个月
🔄 并行事件：日本入侵朝鲜
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 · 52 lines · 8 tokens per session scan A 0c469678b022
timeline is a command published in the GitHub repository wordflowlab/novel-writer (941 stars, last pushed 10mo ago), licensed MIT. It adds 8 tokens to every session and 393 once invoked, about $0.0000 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-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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.