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 jedikim/storyai --skill story-reviewgit clone --depth 1 https://github.com/jedikim/storyaiWrote 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/jedikim/storyai/story-review)<a href="https://agentmods.dev/skills/jedikim/storyai/story-review"><img src="https://agentmods.dev/badge/skills/jedikim/storyai/story-review/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/jedikim/storyai/story-review"><img src="https://agentmods.dev/badge/skills/jedikim/storyai/story-review.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.00085 | $0.00691 |
| Opus 5 | $0.00043 | $0.00345 |
| Sonnet 5 | $0.00017 | $0.00138 |
| Haiku 4.5 | $0.00009 | $0.00069 |
Grade A, and why
story-review 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.
What it actually says
연속성 검수
중요 — 고치지 마세요
이 스킬은 읽기 전용입니다. 발견한 문제를 진단으로 기록하고 사람에게 보고할 뿐, 원고나 그래프를 수정하지 않습니다. 고치면서 새 모순을 만드는 것이 가장 흔한 실패입니다. 수정은 다음 집필 턴이나 사람이 합니다.
1. 결정론 진단부터
check(scope="book", severity="error")
check(scope="book", severity="warn")
이 규칙들은 LLM 없이 그래프 연산으로 돌아갑니다. 여기서 나온 건 확정된 문제입니다.
2. 복선 부채 확인
promises(status=["hypothetical"], sort="debt") # 방치 위험
promises(status=["eligible"], sort="age") # 오래 대기 중
원고가 끝나가는데 hypothetical이 남아 있으면 방치된 복선입니다.
트리거가 정의되지 않은 복선은 회수 가능 여부 자체를 판정할 수 없으니 별도로 보고하세요.
3. 검증 예산은 중반부와 고엔트로피 구간에
장편의 일관성 오류는 서사 위치 40~60% 구간에 몰리고, 문장 엔트로피가 높은 구간에 몰립니다. 전 구간을 균등하게 훑지 말고 그쪽에 시간을 쓰세요.
4. 결정론이 못 잡는 것
의미적 모순은 규칙으로 안 잡힙니다. 의심되는 지점은
trace로 인과 경로를 따라가고 refs로 그 요소를 건드리는 씬을 전부 본 뒤 판단하세요.
5. 보고
각 진단마다 이렇게 남깁니다.
- 무엇이 어긋났는가 (한 문장)
- 근거 — 원문 인용과 위치 두 곳 이상
- 어느 쪽이 틀렸다고 보는가, 그리고 왜
- 고치면 무엇이 함께 바뀌는가 (
impact로 확인)
contradicts 간선을 남기는 것까지가 이 스킬의 쓰기 권한입니다.
그 이상은 하지 마세요.
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 · 60 lines · 85 tokens per session scan A 017e0be66ec7
story-review is a skill published in the GitHub repository jedikim/storyai (0 stars, last pushed 18d ago), licensed MIT. It adds 85 tokens to every session and 691 once invoked, about $0.0004 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…