Borrowing it
Nothing to install: this file belongs to nerds-odd-e/doughnut. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nerds-odd-e/doughnut/main/.agents/skills/dough-resplit-story/SKILL.mdgit clone --depth 1 https://github.com/nerds-odd-e/doughnutWrote 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/nerds-odd-e/doughnut/dough-resplit-story)<a href="https://agentmods.dev/skills/nerds-odd-e/doughnut/dough-resplit-story"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-resplit-story/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/nerds-odd-e/doughnut/dough-resplit-story"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-resplit-story.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.00062 | $0.00919 |
| Opus 5.5 | $0.00025 | $0.00368 |
| Sonnet 5.5 | $0.00012 | $0.00184 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
dough-resplit-story 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 1mo 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resplit story
Replace one large story with smaller stories and partition its refined slice plan to match. A recommendation from slice-plan refinement alone does not authorize this workflow. Do not implement product code.
Resolve context
Require the original story and seed, its refined slice plan, and this project's seed, anchor, plan-location, and lifecycle conventions. Identify completed work, evidence, current decisions, and any existing backlog entry. Resolve backlog context when the original is queued or queueing is requested. If required context or a linked skill is unavailable, name what is missing and stop the affected activity before writing.
Establish smaller stories
Use dough-story-decomposition to decompose the original outcome and order the smaller stories. Supply the original story's established decisions and learning from refinement; reuse answered questions. Keep decomposition's seed non-executable and perform the plan mapping below only after story boundaries and order are resolved.
Split by useful outcomes, not by distributing slices into equal-sized groups. Account for the original scope across the new stories; surface proposed scope removal or changed outcomes for human resolution. Preserve unrelated siblings and stable links. Retain a trace from the original story to its replacements using this project's lifecycle conventions, so it is not left as competing work or recorded as delivered merely because it was split.
Map and realign plans
Map every original slice and its promises to the story it serves. Preserve completed work, compatible evidence, overrun history, and still-relevant decisions. Split or realign slices spanning story boundaries; do not duplicate implementation work or proof ownership. Record genuine dependencies explicitly.
Partition the original plan into one plan per new story using this project's locations. Reuse the original plan for the first story where the lifecycle allows; otherwise retain a replacement trace and retire the competing plan. Link every plan to its canonical story and account for every original slice.
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.
- 1mo ago First seen · 91 lines · 62 tokens per session scan A 2367808bfc7d
dough-resplit-story is a skill published in the GitHub repository nerds-odd-e/doughnut (50 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 919 once invoked, about $0.0002 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-10.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…