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/shizhangyu-foreshadow)<a href="https://agentmods.dev/commands/wordflowlab/novel-writer/shizhangyu-foreshadow"><img src="https://agentmods.dev/badge/commands/wordflowlab/novel-writer/shizhangyu-foreshadow/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/shizhangyu-foreshadow"><img src="https://agentmods.dev/badge/commands/wordflowlab/novel-writer/shizhangyu-foreshadow.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.02220 |
| Opus 5 | $0.00000 | $0.01110 |
| Sonnet 5 | $0.00000 | $0.00444 |
| Haiku 4.5 | $0.00000 | $0.00222 |
Grade A, and why
shizhangyu-foreshadow 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
伏笔管理系统
石章鱼式的伏笔布局大师，管理千里伏脉，打造意外结局。
使用方法
/shizhangyu-foreshadow <操作> [参数]
操作类型
add- 添加新伏笔list- 查看伏笔清单track- 追踪伏笔状态activate- 激活伏笔resolve- 回收伏笔analyze- 分析伏笔布局suggest- 获取伏笔建议check- 检查逻辑链
伏笔类型
物件伏笔
- 信物、密函、令牌、地图
- 看似普通实则关键的物品
- 遗失物品的去向
- 神秘礼物的来源
对话伏笔
- 无意中透露的信息
- 预言和谶语
- 双关语和暗示
- 看似玩笑的真话
事件伏笔
- 看似巧合的相遇
- 微小但异常的事件
- 背景中发生的事
- 被忽略的细节
人物伏笔
- 神秘的身世
- 隐藏的身份
- 未说出的秘密
- 失踪的关键人物
示例用法
添加伏笔
用户：/shizhangyu-foreshadow add 第3章主角捡到的玉佩
AI：
【伏笔登记成功】
伏笔编号：F2024001
━━━━━━━━━━━━━━━━━━
类型：物件伏笔
章节：第3章
位置：第3章第15段
内容：主角在古战场捡到一枚残破玉佩
详细描述：
玉佩材质特殊，似玉非玉，上有半个"陈"字，背面刻着残缺的龙纹。主角以为是普通古物，随手收入囊中。
潜在指向：
1. 可能是前朝皇室信物
2. 可能是某个重要人物的身份证明
3. 可能是开启某个秘密的钥匙
4. 可能与主角身世有关
建议回收时机：
- 近期（5-10章）：作为身份证明
- 中期（20-30章）：揭示重要线索
- 远期（40-50章）：关键转折道具
- 结局：最终真相的证据
关联伏笔：
- F2023098：第1章提到的陈国覆灭
- F2023099：第2章老者说的"天命在陈"
状态：已埋设 [待激活]
查看伏笔清单
用户：/shizhangyu-foreshadow list
AI：
【伏笔追踪表】
━━━━━━━━━━━━━━━━━━
待激活伏笔（12个）
────────────────
F2024001 | 第3章 | 玉佩 | 物件 | 高优先级
F2024002 | 第5章 | "他还活着" | 对话 | 中优先级
F2024003 | 第7章 | 黑衣人 | 人物 | 高优先级
F2024004 | 第9章 | 预言诗 | 对话 | 低优先级
[更多...]
已激活伏笔（5个）
────────────────
F2023095 | 第2章 | 剑痕 | 事件 | 激活于第15章
F2023096 | 第4章 | 梦境 | 事件 | 激活于第18章
[更多...]
已回收伏笔（8个）
────────────────
F2023090 | 第1章 | 开篇死者 | 人物 | 第20章揭晓身份
F2023091 | 第1章 | 密信 | 物件 | 第22章破解内容
[更多...]
伏笔网络图：
F2024001 ─── F2023098
╲ ╱
F2023099
╱ ╲
F2024003 ─── F2024002
优先回收建议：
1. F2024001（玉佩）- 建议在第25章回收
2. F2024003（黑衣人）- 建议在第28章揭示
3. F2024002（对话）- 建议在第30章呼应
激活伏笔
用户：/shizhangyu-foreshadow activate F2024001
AI：
【伏笔激活方案】
伏笔：F2024001（玉佩）
━━━━━━━━━━━━━━━━━━
激活场景设计：
第25章建议情节：
陈平安被困皇宫密室，四面楚歌之际，无意中触碰怀中玉佩。突然，密室墙壁发出轰鸣，一道暗门缓缓开启。
"这是......"跟随而来的老太监瞪大了眼睛，颤声道："陈国皇室的传承信物！老奴等了六十年，终于等到了！"
激活要点：
1. 时机：主角陷入绝境
2. 方式：意外触发
3. 效果：形势逆转
4. 深化：引出更大秘密
后续连锁：
- 揭示主角真实身世
- 引出陈国遗老势力
- 激活F2023098、F2023099
- 埋设新伏笔：传承的代价
写作建议：
不要一次说明所有，保留悬念。玉佩只是钥匙，真正的秘密还在后面。
分析伏笔布局
用户：/shizhangyu-foreshadow analyze
AI：
【伏笔布局分析报告】
整体评估
━━━━━━━━━━━━━━━━━━
伏笔密度：8.5/10（优秀）
逻辑连贯性：9/10（极佳）
回收及时性：7/10（良好）
惊喜程度：8/10（优秀）
布局特点：
1. 长中短线结合合理
2. 不同类型伏笔均衡
3. 关键伏笔相互关联
4. 主线伏笔链条完整
存在问题：
1. 第10-15章伏笔较少
2. F2023094号伏笔过于明显
3. 部分短线伏笔未及时回收
优化建议：
1. 在第12章增加一个中等伏笔
2. 将F2023094做隐藏处理
3. 尽快回收F2023092、F2023093
伏笔网络健康度：
核心链：████████░░ 85%
支线链：███████░░░ 70%
独立点：████░░░░░░ 40%
预期效果：
按当前布局，结局反转冲击力：★★★★☆
读者二刷发现彩蛋概率：95%
逻辑自洽程度：98%
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 · 275 lines · 0 tokens per session scan A c27a07e288b7
shizhangyu-foreshadow is a command published in the GitHub repository wordflowlab/novel-writer (944 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,220 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.