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/Xiaoyangy/novel-studioWrote 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/xiaoyangy/novel-studio/story-short-analyze)<a href="https://agentmods.dev/commands/xiaoyangy/novel-studio/story-short-analyze"><img src="https://agentmods.dev/badge/commands/xiaoyangy/novel-studio/story-short-analyze/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/xiaoyangy/novel-studio/story-short-analyze"><img src="https://agentmods.dev/badge/commands/xiaoyangy/novel-studio/story-short-analyze.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.00027 | $0.00049 |
| Opus 5 | $0.00014 | $0.00024 |
| Sonnet 5 | $0.00005 | $0.00010 |
| Haiku 4.5 | $0.00003 | $0.00005 |
Grade A, and why
story-short-analyze 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.
This is a copy
100% identical to story-short-analyze — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
请使用 story-short-analyze skill，帮助我拆解短篇小说。
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 · 6 lines · 27 tokens per session scan A 90ac1d9ea6a9
story-short-analyze is a command published in the GitHub repository Xiaoyangy/novel-studio (107 stars, last pushed 2d ago), licensed Apache-2.0. It adds 27 tokens to every session and 49 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to story-short-analyze, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
story-short-scan
A tool for scanning and analysing popular short web-fiction rankings on platforms such as Zhihu Yanyan and Fanqie Short Stories.
spec
Spec-driven development — brainstorm, plan, review, and execute with quality gates and approval.
analyze
Analyze Claude Code transcripts to surface subagent behavior and improvement opportunities.
doc-gen
Generate documentation from source code — docstrings, README sections, API references.
refactor
Code-level refactoring analysis and roadmap generation.
agentos-status
Show AgentOS system status — agents, workers, health.