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 Natsummerance/readMD --skill story-reviewgit clone --depth 1 https://github.com/Natsummerance/readMDWrote 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/natsummerance/readmd/story-review)<a href="https://agentmods.dev/skills/natsummerance/readmd/story-review"><img src="https://agentmods.dev/badge/skills/natsummerance/readmd/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/natsummerance/readmd/story-review"><img src="https://agentmods.dev/badge/skills/natsummerance/readmd/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.00043 | $0.00409 |
| Opus 5 | $0.00022 | $0.00204 |
| Sonnet 5 | $0.00009 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
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 10d 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
89% identical to story-review — 4 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 Review
Analytical review of existing prose. This skill is for diagnosis, not
rewriting. Keep /reader-sim separate when the task needs a felt first-time
reader experience rather than analytical critique.
Choose the review level before reading. Start big before small unless the caller explicitly asks for a late-stage pass. The edit levels move from structural to surface, and each assumes the levels above it are stable:
- Editorial review — holistic third-party book-editor pass. What kind of revision does this draft need, and in what order?
- Developmental edit — structure, promise, causality, pacing, character arc. Is the draft the right shape?
- Line edit — voice, rhythm, clarity, texture. Does the prose move well?
- Copyedit — grammar, usage, punctuation, consistency. Is it correct?
- Proofreading — final surface pass. What slipped through?
Each level has a dedicated resource with method and checklist:
resources/editorial-review.mdresources/developmental-edit.mdresources/line-edit.mdresources/copyedit.mdresources/proofreading.md
For adversarial craft critique (as opposed to editorial review), load:
resources/prose-critique.md— methodology and focus-area routing.resources/prose-critique/— deep resources per focus area (structure, character, voice, prose, continuity).
When review incorporates reader-sim data:
resources/reader-sim-signal.md— how to interpret and synthesize reader-sim output alongside analytical critique.
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- resources/copyedit.md 2.9 KB
- resources/developmental-edit.md 3.0 KB
- resources/editorial-review.md 4.8 KB
- resources/line-edit.md 2.5 KB
- resources/proofreading.md 2.7 KB
- resources/prose-critique.md 5.9 KB
- resources/prose-critique/analyze.py 8.8 KB runs code
- resources/prose-critique/antipatterns.md 4.7 KB
- resources/prose-critique/baseline.md 3.0 KB
- resources/prose-critique/character.md 3.8 KB
- resources/prose-critique/continuity.md 3.9 KB
- resources/prose-critique/prose.md 6.5 KB
- resources/prose-critique/structure.md 3.2 KB
- resources/prose-critique/voice.md 4.2 KB
- resources/reader-sim-signal.md 3.0 KB
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.
- 10d ago First seen · 45 lines · 43 tokens per session scan A 33a57a6f00fa
story-review is a skill published in the GitHub repository Natsummerance/readMD (22 stars, last pushed 6d ago), licensed MIT. It adds 43 tokens to every session and 409 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to story-review, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
bibverify
Verify, repair, explain, and generate BibTeX references with Bibverify's DOI-first CLI and MCP tools.
electron-expert
Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.
memory
Use this skill when Pioneer should proactively use durable memory or recalled context: decide whether memory can improve a turn, answer from remembered user/project facts, request memory tools, search/list/get stored memories, save durable preferences or project decisions, forget memories, audit or clean up memory, or…
trellis-brainstorm
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex…
trellis-update-spec
Captures executable contracts and coding conventions into .trellis/spec/ documents. Use when learning something valuable from debugging, implementing, or discussion that should be preserved for future sessions.