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 bs779517/story-skills --skill chapter-writinggit clone --depth 1 https://github.com/bs779517/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/bs779517/story-skills/chapter-writing)<a href="https://agentmods.dev/skills/bs779517/story-skills/chapter-writing"><img src="https://agentmods.dev/badge/skills/bs779517/story-skills/chapter-writing/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/bs779517/story-skills/chapter-writing"><img src="https://agentmods.dev/badge/skills/bs779517/story-skills/chapter-writing.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.00055 | $0.00859 |
| Opus 5 | $0.00028 | $0.00430 |
| Sonnet 5 | $0.00011 | $0.00172 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
chapter-writing 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chapter Writing
Overview
Write story chapters using an outline-first workflow. Gathers context from all other story elements (characters, world, plot) to maintain consistency, builds a beat-by-beat outline for approval, then writes full prose. After writing, updates all cross-references (chapter index, timeline, foreshadowing).
Prerequisites
A story project must already exist with at least:
story.md(story bible)- At least one character in
characters/ - A plot structure in
plot/_index.md(recommended but not required for first chapters)
Outline-First Workflow
1. Gather Context
Read these files to understand the current story state:
story.md- genre, themes, POV, tensechapters/_index.md- what's been written, current word countplot/_index.md- arc status, what needs to happen nextplot/timeline.md- chronological position
If this isn't the first chapter, also read:
- The previous chapter file - for continuity (ending state, cliffhangers, emotional tone)
- Active arc files in
plot/arcs/- for upcoming plot beats
2. Determine Chapter Scope
Ask the user:
- What should this chapter cover? (or suggest based on plot arcs)
- Whose POV?
- Which location(s)?
If plot arcs exist, suggest the next logical beats to advance.
3. Build the Outline
Create a beat-by-beat outline listing:
- Each scene/beat and what it accomplishes
- POV character and location for each beat
- Which arc plot points are advanced
- Any foreshadowing to plant or pay off
Load the POV character's file for voice reference. Load relevant location files for setting details.
Present the outline to the user for approval. Revise until approved.
4. Write the Chapter
With the approved outline, write the full prose:
- Follow the POV and tense from
story.md - Use the POV character's voice and speech patterns from their profile
- Ground scenes in location details from worldbuilding files
- Consult
references/writing-guidelines.mdfor prose craft guidance - Use the chapter template from
references/chapter-template.md - Include the approved outline in the file above the prose (for reference)
What ships with it
2 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.
- 11d ago First seen · 97 lines · 55 tokens per session scan A c81a6ae41802
chapter-writing is a skill published in the GitHub repository bs779517/story-skills (8 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 859 once invoked, about $0.0003 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
visionaire-verify
Verify rendered CSS/layout truth after EVERY visual edit using the Visionaire MCP tools. Use this skill whenever you change CSS, HTML structure, layout, spacing, alignment, colors, responsive breakpoints, or any styling — even if the user did not explicitly ask you to "verify". Claude cannot see rendered pixels; this…
refactoring-ui
Apply UI design principles from Refactoring UI by Adam Wathan & Steve Schoger. Covers visual hierarchy (size, weight, color, spacing), layout systems (spacing scales, grids), typography (type scales, line-height, alignment), color (HSL palettes, shade systems, accessible contrast), depth (shadow elevation, overlap)…
auri-core
Auri: assistente de voz inteligente (Alexa + Claude claude-opus-4-20250805). Visao do produto, persona Vitoria Neural, stack AWS, modelo Free/Pro/Business/Enterprise, roadmap 4 fases, GTM, north star WAC e analise competitiva.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
skill-writing-plans
Create zero-context implementation plans with bite-sized tasks — use for multi-step feature planning.