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 submissiongit 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/submission)<a href="https://agentmods.dev/skills/danjdewhurst/story-skills/submission"><img src="https://agentmods.dev/badge/skills/danjdewhurst/story-skills/submission/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/submission"><img src="https://agentmods.dev/badge/skills/danjdewhurst/story-skills/submission.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.00201 | $0.04158 |
| Opus 5.5 | $0.00080 | $0.01663 |
| Sonnet 5.5 | $0.00040 | $0.00832 |
| Haiku 4.5 | $0.00020 | $0.00416 |
Grade A, and why
submission 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 8d 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submission
Overview
Get a finished manuscript out the door. This skill checks submission
readiness, drafts the submission package (query letter, pitch, synopsis,
blurb, comp titles), builds the manuscript in submission format, and keeps a
tracker of where the book has gone. Package files live under submission/
in the story project. The author sends every submission themselves; this
skill prepares materials and records outcomes.
Prerequisites
A story project with a complete or near-complete draft. Verify story.md
exists in the project root and read its status, genre, sub-genre,
premise, author (or authors for a co-written book), contact, and language fields. If status is not complete or
revising, tell the user the package can be drafted now but the readiness
check will fail until the draft is finished.
Language And Market
language (a missing field means en) is the book's language. Ask which
market the user is submitting to. The query letter, Shunn manuscript
format, comp conventions, and word-count norms in the references are the
English-language (mainly US and UK) market's. Other markets have their
own practice: some publishers take submissions directly rather than
through agents, and many ask for a synopsis and sample pages in their own
format. Ask the user for the guidelines of the agents or publishers they
are targeting and follow those; never present English-market conventions
as universal. Write the package in the language the agent or publisher
reads, which is usually the book's.
When to Use
- Checking whether a manuscript is ready to submit
- Drafting or revising a query letter, pitch, synopsis, blurb, or comp list
- Building a Shunn-format manuscript for agents or magazines
- Writing a retailer or back-cover description for self-publishing
- Recording queries sent and responses received
- Submitting short fiction to magazines, anthologies, or contests: simultaneous or exclusive submissions, rights, response windows, and status queries
- Choosing and ordering the stories for a collection, and its previously-published acknowledgements
- NOT for self-publishing production (ISBNs, retailer metadata, print
interiors, launch, rights deals and contracts): use the
publishingskill. This skill still drafts the blurb and retailer description it uses, and records the rights a short-fiction market buys - NOT for pitching a series of several books or writing its series overview
(use
series-continuity); the query for book one is still drafted here - NOT for revising the manuscript itself (use
revision-continuity) - NOT for reader feedback rounds (use
feedback-triage)
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.
- 8d ago Changed 7ab93a0aaa0d
- 14d ago Changed · +7 lines a449af445feb
- 15d ago Changed · +11 lines · +56 tokens per session cd046c9803c2
- 16d ago Changed · +45 lines · +39 tokens per session 0e5ec93bee96
- 20d ago Changed · +19 lines 444cd687bb9e
- 25d ago Changed · +25 lines 40bf0826ca42
- 27d ago Changed · +10 tokens per session ed0cdecd0de5
- 28d ago Changed · +19 lines 106c10639914
- 1mo ago First seen · 196 lines · 96 tokens per session scan A 0bc7d494b95c
submission is a skill published in the GitHub repository danjdewhurst/story-skills (341 stars, last pushed 2d ago), licensed MIT. It adds 201 tokens to every session and 4,158 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-23.
Other skills, from other repositories
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:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
alive-create
Scaffold a new walnut -- venture, experiment, person, life area, project.
alive-project
Regenerate now.json projections for all walnuts (mechanical, no approval needed).
tasks
View and manage the task stack and processing queue. Shows pending work, active tasks, completed items, and queue state. Triggers on "/tasks", "show tasks", "what's pending", "task list", "queue status".