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.
npx skills add wordflowlab/novel-writer-skills --skill mysterygit clone --depth 1 https://github.com/wordflowlab/novel-writer-skillsWrote 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/skills/wordflowlab/novel-writer-skills/mystery)<a href="https://agentmods.dev/skills/wordflowlab/novel-writer-skills/mystery"><img src="https://agentmods.dev/badge/skills/wordflowlab/novel-writer-skills/mystery/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/skills/wordflowlab/novel-writer-skills/mystery"><img src="https://agentmods.dev/badge/skills/wordflowlab/novel-writer-skills/mystery.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.00037 | $0.02766 |
| Opus 5 | $0.00018 | $0.01383 |
| Sonnet 5 | $0.00007 | $0.00553 |
| Haiku 4.5 | $0.00004 | $0.00277 |
Grade A, and why
mystery-novel-conventions 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 13d 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
悬疑推理小说创作规范
快速参考
| 元素 | 指导原则 | 位置 |
|---|---|---|
| 触发事件 | 案件/谜团发生 | 前 10% |
| 误导线索 | 错误的引导 | 贯穿全文，3-5 个 |
| 真实线索 | 公平游戏的证据 | 75% 之前 |
| 真相揭露 | 真相揭示 | 85-95% |
| 收尾 | 结束所有线索 | 最后 5% |
核心原则
公平游戏原则
黄金法则：读者必须在侦探之前获得所有解决谜团所需的线索。
-
没有隐藏信息
- 所有关键线索都必须呈现给读者
- 侦探不能基于读者不知道的信息破案
- 只在结尾揭示的秘密证据违反公平游戏
-
逻辑推理
- 解决方案必须能从呈现的事实中逻辑推导
- 巧合可以使情况复杂化，但永远不能解决
- 直觉可以，但必须基于已展示的证据
-
不使用机械降神
- 不能突然出现新角色作为罪犯
- 不能有之前未提及的能力或工具
- 不能有神的干预或纯粹的运气
悬疑小说结构
第一幕：铺垫（0-25%）
建立常态世界：
- 介绍主角和他们的世界
- 展示角色能力
- 埋下性格怪癖的种子
案件发生：
- 在前 10% 发生
- 必须足够有趣/不寻常以证明调查的必要性
- 风险应该清晰
初步调查：
- 主角接受案件
- 首次访谈和证据收集
- 建立关键嫌疑人
第二幕：调查（25-75%）
收集线索：
- 呈现所有公平游戏的证据
- 混合真实线索与误导线索
- 每条线索都应该感觉重要
误导线索：
- 3-5 条看似有希望的虚假线索
- 必须足够可信以误导
- 最终通过逻辑调查证伪
复杂化升级：
- 新证据与旧理论矛盾
- 嫌疑人有不在场证明或秘密
- 风险升级（更多案件、主角面临危险）
中点转折（约 50%）：
- 重新框架谜团的重大揭示
- 主角的理论被证明错误
- 新角度出现
第三幕：解决（75-100%）
黑暗之夜（75-85%）：
- 主角似乎被难住
- 所有理论都失败了
- 绝望或怀疑的时刻
真相揭露（85-95%）：
- 关键洞察连接所有点
- 主角重构真相
- 与罪犯对峙
收尾（95-100%）：
- 解释如何/为什么
- 所有松散的线索被收紧
- 正义得到伸张（或有意颠覆）
线索布置策略
线索类型
物理证据：
- 物品、指纹、DNA
- 必须在需要之前埋下
- 重要性最初可能不清楚
证言证据：
- 证人陈述
- 不在场证明及其矛盾
- 谎言（有意或无意）
行为证据：
- 角色对事件的反应
- 不寻常的行为模式
- 通过行动揭示的动机
circumstantial证据：
- 机会、手段、动机
- 模式和联系
- 时间线不一致
线索布置时机
早期线索（0-25%）：
- 建立基准事实
- 埋下看似无辜的种子
- 介绍所有关键嫌疑人
中期线索（25-75%）：
- 混合真实线索与误导线索
- 使情况复杂化
- 揭示角色动机
后期线索（75-85%）：
- 使其可解的最后一块拼图
- 可以是一直存在的东西
- 主角的顿悟时刻
误导线索最佳实践
有效的误导线索
特征：
- 足够可信以显得真实
- 有一些证据支持
- 最终通过逻辑被证伪
- 揭示为虚假时不显得廉价
示例：
- 有强烈动机但坚实不在场证明的嫌疑人
- 被栽赃的有罪证据
- 巧合出现在犯罪现场
- 看起来有罪但实际无辜的秘密活动
常见错误
❌ 太明显：读者立即看穿 ❌ 太勉强：感觉强迫和人为 ❌ 从不解释：悬而未决没有解决 ❌ 太多：读者失去追踪并感到沮丧
嫌疑人管理
经典设置
至少 3 个嫌疑人：
- 每个都需要动机、手段和机会
- 每个在某个时刻都应该显得有罪
- 至少一个应该是同情的
罪犯：
- 应该在介绍的角色中（公平游戏）
- 必须有最终揭示的逻辑动机
- 他们有罪的线索必须从早期就存在
误导嫌疑人：
- 最明显的选择
- 强烈的动机和间接证据
- 最终通过调查被排除
同情嫌疑人：
- 读者希望不是有罪的
- 有值得保护的秘密
- 通常帮助解决真正的谜团
角色秘密
每个嫌疑人都应该有秘密：
- 不是所有秘密都与案件相关
- 秘密创造误导
- 揭示秘密推进调查
- 有些秘密比案件更具破坏性
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.
- 13d ago First seen · 338 lines · 37 tokens per session scan A fbdb55abc0d5
mystery-novel-conventions is a skill published in the GitHub repository wordflowlab/novel-writer-skills (258 stars, last pushed 10mo ago), licensed MIT. It adds 37 tokens to every session and 2,766 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…