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 series-continuitygit 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/series-continuity)<a href="https://agentmods.dev/skills/danjdewhurst/story-skills/series-continuity"><img src="https://agentmods.dev/badge/skills/danjdewhurst/story-skills/series-continuity/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/series-continuity"><img src="https://agentmods.dev/badge/skills/danjdewhurst/story-skills/series-continuity.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.00136 | $0.03683 |
| Opus 5.5 | $0.00054 | $0.01473 |
| Sonnet 5.5 | $0.00027 | $0.00737 |
| Haiku 4.5 | $0.00014 | $0.00368 |
Grade A, and why
series-continuity 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Series Continuity
Overview
Plan and maintain sequels, prequels, and companion books as linked Story Skills projects. Each book stays a standalone project with its own story.md, characters, world, chapters, and continuity files. Books point at each other through story.md frontmatter, and story series checks the canon they share.
series- kebab-case series id shared by every book, such asthe-ember-cycleseries-title- optional retail series name, such asThe Ember Cycle, that the metadata sheet prints in place of the idbook-number- publication order (1, 2, 3...);0for a prequel published later, a decimal such as1.5for a between-books novellafollows- paths to books set earlier in the story's chronologyprecedes- paths to books set later in the story's chronology
Chronology and publication order are separate. A prequel written after the first book has book-number: 2 and lists ../book-one under precedes.
This skill owns the book-level layer: linked books and the canon they share. The within-serial installment layer — how serial or episodic installments are structured — is covered by the genre-craft skill's serial/episodic structure reference.
Links are relative paths from the book root, and every link needs a matching backlink: if book two lists ../book-one under follows, book one must list ../book-two under precedes. Keep sibling books in the same parent folder so the paths stay short and portable.
When to Use
- Starting a sequel, prequel, interquel, or companion book to an existing project
- Carrying characters, locations, systems, factions, artifacts, or glossary terms into another book
- Revising a book that other books in the series depend on
- Keeping a series bible, or planning and pitching a series of several books (see
references/series-bible.md) - NOT for a single standalone book (use
story-init), for within-book continuity (userevision-continuity), or for the query letter, pitch, or synopsis of a single book (usesubmission). A series pitch stays here: the series overview and the series line in book one's query (seereferences/series-bible.md)
What ships with it
1 file 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 323812868590
- 19d ago Changed · +5 lines 8c33f200af5b
- 20d ago Changed · -14 lines · +34 tokens per session d37af84dcc77
- 21d ago Changed · +9 lines · +22 tokens per session 072e0e71bee6
- 24d ago Changed d4f759fa0124
- 29d ago Changed f866e3506e3f
- 1mo ago Changed · +5 lines 509365aa0531
- 1mo ago Changed · +2 lines bc60061e6ae6
- 1mo ago Changed · +1 lines cf9fdd94107c
- 1mo ago First seen · 143 lines · 80 tokens per session scan A 10c7cf63c1f3
series-continuity is a skill published in the GitHub repository danjdewhurst/story-skills (361 stars, last pushed today), licensed MIT. It adds 136 tokens to every session and 3,683 once invoked, about $0.0005 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-09-17.
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…