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 QQQingyu/story-snack --skill fill-biblegit clone --depth 1 https://github.com/QQQingyu/story-snackWrote 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/qqqingyu/story-snack/fill-bible)<a href="https://agentmods.dev/skills/qqqingyu/story-snack/fill-bible"><img src="https://agentmods.dev/badge/skills/qqqingyu/story-snack/fill-bible/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/qqqingyu/story-snack/fill-bible"><img src="https://agentmods.dev/badge/skills/qqqingyu/story-snack/fill-bible.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.00036 | $0.01155 |
| Opus 5 | $0.00018 | $0.00577 |
| Sonnet 5 | $0.00007 | $0.00231 |
| Haiku 4.5 | $0.00004 | $0.00115 |
Grade A, and why
fill-bible 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 12d 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
填充设定
引导用户逐步填充 bible/ 下的模板文件，完成世界观搭建。
流程
按以下顺序，每次只问一个方面，等用户回答后再填充对应文件：
1. 题材选择（核心步骤）
- 问：你想写什么类型的小说？
- 列出常见选项供参考：悬疑推理、言情、奇幻、科幻、都市现实、历史、恐怖、武侠、校园、末世……
- 也可以是混合题材（如「悬疑+言情」「科幻+恐怖」）
- 追问：目标基调（暗黑/轻松/治愈/热血/...）、目标读者、连载平台
- 记录题材信息，后续步骤会据此适配提问内容
2. 故事背景
- 问：时代（现代/民国/近未来/架空/古代/...）、地点特征、社会氛围
- 填充：
bible/universe/setting.md
3. 主角设定
- 问：姓名、年龄、职业、性格核心特质、标志性习惯、口头禅
- 根据题材适配追问：
- 悬疑：推理风格（演绎/归纳/直觉）
- 言情：情感模式（主动/被动/回避/...）
- 奇幻/武侠：能力体系、成长路线
- 都市/校园：核心困境、社会身份
- 请用户给 3 句示例台词
- 填充：
bible/characters/protagonist.md
4. 核心配角
- 问：最重要的配角是谁？（搭档/恋人/对手/师长/...）
- 与主角的关系、性格（需与主角形成张力）、说话方式
- 填充：
bible/characters/sidekick.md
5. 常驻配角
- 问：有没有想好的其他重要配角？（可以跳过，后续再补）
- 填充：
bible/characters/recurring.md
6. 世界观规则
- 根据题材生成初始规则建议，问用户是否需要调整
- 重点确认（按题材适配）：
- 通用：暴力尺度、叙事禁区
- 悬疑：是否允许超自然元素、公平推理原则
- 奇幻/科幻：魔法/科技体系的硬度、能力上限
- 言情：情感尺度、是否有竞争对手
- 填充：
bible/universe/rules.md
7. 写作风格
- 根据前面收集的信息，自动生成
bible/style.md中的题材专属部分：- 题材与基调（第一节）
- 基本参数（视角、时态——根据题材建议默认值，让用户确认）
- 题材专属风格（第五节 · 题材专属风格）
- 人物辨识度速查表（第六节）
- 题材专属禁用（第八节 · 题材专属禁用）
- 自我检查清单追加题材专属检查项（第九节）
- 填充：
bible/style.md
8. 主弧大纲
- 问：贯穿全篇的核心长线是什么？最终走向？
- 根据题材适配追问：
- 悬疑：大阴谋是什么？幕后黑手是谁？
- 言情：核心 CP 的终极障碍？是否 HE？
- 奇幻：终极 boss/威胁？主角成长终点？
- 都市：主角的核心困境如何解决？
- 引导用户设计三阶段主弧（铺垫→升级→高潮）
- 填充：
bible/arc/master-arc.md
9. 事件池
- 问：有没有想好的章节事件创意？
- 根据题材适配术语：
- 悬疑：案件创意（密室、不在场证明、身份诡计……）
- 言情：情感事件（误会、重逢、告白、第三者……）
- 奇幻：冒险事件（副本、试炼、新能力觉醒……）
- 通用：冲突事件
- 如果有：帮用户整理成标准格式填入
- 如果没有：根据已有设定自动生成 10 个事件梗概
- 填充：
bible/arc/event-pool.md
完成后
展示设定摘要，确认无误后告知用户：
设定完成！现在可以使用 /write-chapter 开始写第一章。
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.
- 12d ago First seen · 91 lines · 36 tokens per session scan A 9470651a7626
fill-bible is a skill published in the GitHub repository QQQingyu/story-snack (5 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 1,155 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-31.
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…