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 publishinggit 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/publishing)<a href="https://agentmods.dev/skills/danjdewhurst/story-skills/publishing"><img src="https://agentmods.dev/badge/skills/danjdewhurst/story-skills/publishing/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/publishing"><img src="https://agentmods.dev/badge/skills/danjdewhurst/story-skills/publishing.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.00204 | $0.04083 |
| Opus 5.5 | $0.00082 | $0.01633 |
| Sonnet 5.5 | $0.00041 | $0.00817 |
| Haiku 4.5 | $0.00020 | $0.00408 |
Grade A, and why
publishing 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 3d 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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publishing
Overview
Take a final manuscript into readers' hands. This skill fills the
publishing metadata in story.md, writes the copyright page, builds and
checks the ebook and print interior, walks the author through
distribution, pricing, and launch, and keeps an inventory of the rights
the author holds. Planning files live under publishing/ in the story
project. The author makes every account, upload, purchase, payment, and
signature; this skill prepares, checks, and records.
Prerequisites
A story project whose manuscript is final or nearly so. Verify story.md
exists and read title, status, author or authors, genre,
series, book-number, cover, and any publishing fields already set. If
status is not complete, say that metadata and launch planning can start
now but the files must be rebuilt after the last revision.
Language And Market
Read language in story.md (a missing field means en) and ask which
countries the author is publishing in. The book's language decides the
language of the description, keywords, and copyright page; the market
decides the ISBN agency, subject schemes, retailers, and pricing rules.
The references start from the US and UK English-language market and
note the rest: Thema subjects and ISBN agencies elsewhere in
references/metadata-checklist.md, other retail routes and fixed book
prices in references/launch-plan.md, and rights by language and
territory in references/rights-one-sheet.md. Never assume a US retailer, scheme, or
law applies elsewhere; say what to check.
When to Use
- Filling retailer metadata: ISBN, publisher, date, description, keywords, BISAC and Thema subjects, language, cover alt text, AI disclosure
- Writing the copyright page and recording the permission status of quoted
matter (clearance questions go to
editorial-review) - Building and checking the EPUB or the print interior; choosing trim size
- Choosing retailers and exclusivity, setting prices, planning a launch
- Recording rights, reviewing a contract offer, drafting a rights one-sheet
- NOT for query letters, agent submission, synopsis, blurb, or retailer
description drafting (use
submission; this skill reuses its blurb and retailer description) - NOT for audiobook scripts, screenplays, translations, or other formats
(use
adaptation) - NOT for revising the manuscript (use
revision-continuity)
What ships with it
6 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.
- 3d ago Changed 2df54523f65d
- 9d ago Changed · +3 lines b8ec75f32e02
- 10d ago Changed · +23 lines · +13 tokens per session ff64a2aa7b49
- 11d ago Changed · +34 lines d1492b6e15e4
- 15d ago Changed · +21 lines fafeb82de197
- 20d ago Changed · +4 lines e89bb8b16904
- 22d ago Changed · +3 lines 9aa382a18fe6
- 23d ago First seen · 233 lines · 191 tokens per session scan A 5e19fec56f2f
publishing is a skill published in the GitHub repository danjdewhurst/story-skills (323 stars, last pushed 3d ago), licensed MIT. It adds 204 tokens to every session and 4,083 once invoked, about $0.0008 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-25.
Other skills, from other repositories
Use whenever the user works with PDF files — reading/extracting text from PDFs (lecture notes, textbook chapters, HW problems, HW solutions, hand-written answers), converting PDFs to markdown for downstream analysis, merging/splitting PDFs, or creating PDFs. For scanned or hand-written PDFs, OCR is required…
export-pdf
Convert a markdown file to PDF using mdpdf. Use when exporting proposals, SOPs, or any markdown document to PDF.
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
add-pdf-report
Internal implementation skill invoked by /add-native for app-generated PDF report workflows using expo-print and, when present, expo-sharing.
add-pdf-viewer
Internal implementation skill invoked by /add-native for native PDF control workflows. Handles HTTPS and file URI PDF viewing with @microsoft/power-apps-native-pdf-viewer 0.2.9+.
deck-ai
Generate modern presentation decks (PDF) from markdown content. Local open-source alternative to Gamma — uses Slidev for layouts and Unsplash for imagery. Invoke when the user asks to "make a deck", "build slides from this", or "turn this into a presentation".