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 danjdewhurst/story-skills --skill story-maintenancegit clone --depth 1 https://github.com/danjdewhurst/story-skillsWrote 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/danjdewhurst/story-skills/story-maintenance)<a href="https://agentmods.dev/skills/danjdewhurst/story-skills/story-maintenance"><img src="https://agentmods.dev/badge/skills/danjdewhurst/story-skills/story-maintenance/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/danjdewhurst/story-skills/story-maintenance"><img src="https://agentmods.dev/badge/skills/danjdewhurst/story-skills/story-maintenance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00178 | $0.05389 |
| Opus 5.5 | $0.00071 | $0.02156 |
| Sonnet 5.5 | $0.00036 | $0.01078 |
| Haiku 4.5 | $0.00018 | $0.00539 |
Grade A, and why
story-maintenance 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 13d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story Maintenance
Overview
Run deterministic maintenance for Story Skills projects. Use the CLI for structure validation, registry rebuilds, word counts, link checks, continuity checks, project reports, next-action reports, pacing, clue, voice, and name checks, revision-pass tracking, Mermaid diagrams, schema migration, entity helpers, manuscript import, and manuscript export and builds. The creative skills still own story decisions; this skill handles mechanical consistency. It runs a check and reports what it found, and fixes mechanical problems such as broken references and stale registries; deciding what a finding means for the story, and revising the story to fix it, belongs to revision-continuity, plot-structure, voice-style, or genre-craft.
CLI Access
Prefer the first available command:
story <command>- when the package bin is installednode scripts/story.js <command>- bundled fallback, resolvingscripts/story.jsrelative to this skill foldernode <checkout>/bin/story.js <command>- only when the user names a Story Skills repository checkout or you are working in one, where<checkout>is its path
Write the script in forms 2 and 3 as an absolute path and run the command from the folder you would run story from, so . and other relative paths keep their meaning. Use Node, not Bun or the story script in the checkout's package.json: Bun would load that folder's bunfig.toml (which can run code) and .env, and a package script runs from the checkout's root, so . would be the checkout, not the story project.
If none of these are available, perform the requested maintenance manually using the shared conventions in references/conventions.md.
Run the installed or bundled CLI in place. Do not copy scripts/story.js into the user's story project, and do not create project-local build scripts, generator scripts, or bulk writer scripts to generate story content. Story projects should remain markdown-first, plus explicitly requested exports such as dist/manuscript.md.
What ships with it
7 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.
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.
- 13d ago Changed cbfcaf461232
- 20d ago Changed · -79 lines · +24 tokens per session e821d28b0237
- 21d ago Changed · +36 lines · +66 tokens per session 7e5bd6aef4af
- 24d ago Changed d99c2144c372
- 25d ago Changed · +2 lines 0acba815c34c
- 28d ago Changed · +2 lines e72b0cc51d82
- 1mo ago Changed · +14 lines 83a8601d344e
- 1mo ago Changed · +2 lines 40b2855fb909
- 1mo ago Changed · +6 lines 0b8d7df2694b
- 1mo ago First seen · 128 lines · 88 tokens per session scan A d7abab7af8d5
story-maintenance is a skill published in the GitHub repository danjdewhurst/story-skills (361 stars, last pushed today), licensed MIT. It adds 178 tokens to every session and 5,389 once invoked, about $0.0007 per session on Opus 5.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 skills, from other repositories
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:save
The human wants to checkpoint. Or: the stash has grown heavy — 5+ items, 30+ minutes, a natural pause in the work. The squirrel doesn't decide when to save. It surfaces the need and lets the human pull the trigger. Runs the full save protocol: confirms stash, writes log, updates state, generates projections…
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…