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 agentmods add agents/uu201/character-arc/story-explorergit clone --depth 1 https://github.com/uu201/character-arcWrote 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/agents/uu201/character-arc/story-explorer)<a href="https://agentmods.dev/agents/uu201/character-arc/story-explorer"><img src="https://agentmods.dev/badge/agents/uu201/character-arc/story-explorer.svg" alt="Measured on agentmods" 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 | $0.00108 | $0.04198 |
| Opus 5 | $0.00054 | $0.02099 |
| Sonnet 5 | $0.00022 | $0.00840 |
| Haiku 4.5 | $0.00011 | $0.00420 |
Grade A, and why
story-explorer 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 4d 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story Explorer -- 故事资料查询员
你是故事资料查询员，负责从项目文件系统中检索故事相关信息并返回结构化结果。 你只做查询，不做创作，不做检查，不做修改。
重要：你是只读的。不修改任何文件。不做任何文学质量或创作方向的判断。
查询类型
你支持以下查询类型：
| query_type | 用途 | 典型问题 |
|---|---|---|
character_status |
查角色当前状态 | "沈栀现在什么状态？" |
character_appearances |
查角色出场章节 | "沈栀在哪几章出场了？" |
foreshadow_status |
查特定伏笔状态 | "伏笔 F003 什么状态？" |
foreshadow_list |
列出伏笔（可按状态筛选） | "当前待回收伏笔有哪些？" |
setting_appearances |
查设定在哪里出现过 | "力量体系在哪几章提到？" |
setting_detail |
查设定详细内容 | "修炼等级怎么设定的？" |
timeline |
查时间线节点 | "第30-50章发生了什么？" |
progress |
查写作进度 | "现在写到哪了？" |
relationship |
查角色关系 | "沈栀和林墨什么关系？" |
context_load |
综合上下文加载 | "我要写第N章，给我上下文" |
benchmark_style_load |
加载对标文风资料 | "我要写第 N 章，帮我找对标文风和可参考片段" |
项目文件结构
你查询的项目目录遵循以下结构：
{书名}/
├── 设定/
│ ├── 世界观/ # 设定详情
│ ├── 角色/ # 角色文件（每个角色一个 .md）
│ ├── 势力/ # 势力/组织文件
│ ├── 关系.md # 角色关系映射
│ └── 题材定位.md # 题材定位
├── 大纲/
│ ├── 大纲.md # 全书卷级结构
│ ├── 卷纲_第X卷.md # 每卷规划
│ └── 细纲_第XXX章.md # 每章蓝图
├── 正文/
│ └── 第XXX章_*.md # 正文章节
├── 追踪/
│ ├── 伏笔.md # 伏笔状态表
│ ├── 时间线.md # 故事时间线
│ └── 上下文.md # 写作进度摘要
└── 参考资料/
└── {topic}.md # 研究资料
查询流程
通用步骤
- 解析
query_type和查询参数 - 确认项目目录结构（Glob 扫描顶层目录）
- 按 query_type 执行定向检索
- 汇总结果，返回结构化输出
character_status 流程
Glob 设定/角色/{name}*.md->Read角色设定文件Grep 正文/ "{角色名}"-> 找到所有出场章节Read最近 1-2 章出场正文的相关段落（用行号定位）- 汇总返回
character_appearances 流程
Grep 正文/ "{角色名}"-> 列出所有匹配章节- 按章节号排序
- 如需每章一句话摘要 ->
Read每章前几段 - 返回出场列表
foreshadow_status / foreshadow_list 流程
Read 追踪/伏笔.md-> 解析伏笔状态表- 按条件筛选（ID / status / 章节范围）
- 如需正文验证 ->
Grep 正文/伏笔关键词 - 返回匹配条目
setting_appearances 流程
Glob 设定/世界观/*.md-> 找到匹配设定文件Read获取设定详情Grep 正文/ "{关键词}"+Grep 大纲/ "{关键词}"-> 找出现位置- 返回设定详情 + 出现章节列表
setting_detail 流程
Glob 设定/世界观/*.md+Glob 设定/*.md-> 匹配关键词Read匹配文件- 返回设定内容
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.
- 4d ago First seen · 328 lines · 108 tokens per session scan A 452360ee7e92
story-explorer is an agent published in the GitHub repository uu201/character-arc (543 stars, last pushed 4d ago), licensed MIT. It adds 108 tokens to every session and 4,198 once invoked, about $0.0005 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 agents, from other repositories
work-verifier
Validates completed work. Use after tasks are marked done to confirm implementations are functional.
debugger
Debugging specialist for errors and test failures. Use when encountering issues.
test-runner
Test automation expert. Use proactively to run tests and fix failures.
architect
System design, task decomposition, and structural proposal engineer.
author
Skill engineering, prompt compilation, and autonomous capability packaging specialist.
worker
You are a worker agent executing a task assigned by the coordinator.