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 comfuture/novelist --skill novel-story-tellinggit clone --depth 1 https://github.com/comfuture/novelistWrote 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/comfuture/novelist/novel-story-telling)<a href="https://agentmods.dev/skills/comfuture/novelist/novel-story-telling"><img src="https://agentmods.dev/badge/skills/comfuture/novelist/novel-story-telling/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/comfuture/novelist/novel-story-telling"><img src="https://agentmods.dev/badge/skills/comfuture/novelist/novel-story-telling.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.00150 | $0.03940 |
| Opus 5 | $0.00075 | $0.01970 |
| Sonnet 5 | $0.00030 | $0.00788 |
| Haiku 4.5 | $0.00015 | $0.00394 |
Grade A, and why
novel-story-telling 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.
How it starts
The opening of the file, as written. The whole thing — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Novel Story Telling
Before running a bundled command, resolve <skill-dir> to the absolute directory
containing this SKILL.md. Keep --project-root pointed at the active novel
workspace, not at the skill or plugin installation.
Operating Contract
Treat chapters/ as manuscript canon and all other source directories as planning and continuity evidence. Follow AGENTS.md. Never edit published/ as source.
Write all agent instructions, temporary prompts, schemas, and script inputs in English. Write manuscript prose and author-facing creative output in this order of precedence:
- the language explicitly requested by the author;
project.mdlanguage;style/000.style-guide.mdlanguage;- the dominant language of recent chapters.
Preserve names, honorifics, invented terms, and spelling from canonical files. Do not translate them unless requested.
Resolve conflicts by authority: explicit author direction > final source > revision source > latest manuscript fact > draft source > outline or seed. Report unresolved conflicts; do not silently choose or invent canon.
Analytical Review Routing Boundary
Keep analytical review separate from ordinary planning, drafting, and revision.
Do not invoke analytical-review unless the author explicitly requests
critique/review or explicitly delegates the complete autonomous novel lifecycle
from initial planning through publication.
For that fully autonomous start-to-publication request only, after all chapters
are drafted and before calling publish-novel:
- run whole-manuscript
analytical-review; - record each material finding as
apply,defer, orrejectwith a concise rationale; - apply selected findings through this storytelling workflow and update canon;
- run one bounded analytical regression review;
- complete strict continuity validation;
- call
publish-novelfor deterministic packaging.
An ordinary request to finish remaining chapters, revise known material, or publish an existing manuscript does not by itself authorize this loop. If the author explicitly asks for review and revision together, keep diagnosis and application distinct and preserve finding IDs through the handoff.
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.
- agents/openai.yaml 273 B
- references/drama.md 5.8 KB
- references/mystery.md 6.9 KB
- references/romantic-entanglement.md 7.0 KB
- references/science-fiction.md 7.0 KB
- references/story-flow.md 13 KB
- references/time-travel-and-loop.md 7.6 KB
- references/wuxia.md 7.6 KB
- scripts/build_story_context.py 8.6 KB runs code
- scripts/check_continuity.py 18 KB runs code
- scripts/story_io.py 7.7 KB runs code
- scripts/update_story_ledger.py 7.4 KB runs code
- scripts/write_chapter.py 7.5 KB runs code
- tests/test_chapter_markup.py 4.8 KB runs code
- tests/test_story_ledger.py 2.4 KB runs code
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 · 327 lines · 150 tokens per session scan A 847f60e41b18
novel-story-telling is a skill published in the GitHub repository comfuture/novelist (5 stars, last pushed 1mo ago), licensed MIT. It adds 150 tokens to every session and 3,940 once invoked, about $0.0007 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…