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-slice-plan-refinement/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-slice-plan-refinement)<a href="https://agentmods.dev/skills/nerds-odd-e/doughnut/dough-slice-plan-refinement"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-slice-plan-refinement/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-slice-plan-refinement"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-slice-plan-refinement.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.00086 | $0.01661 |
| Opus 5.5 | $0.00034 | $0.00664 |
| Sonnet 5.5 | $0.00017 | $0.00332 |
| Haiku 4.5 | $0.00009 | $0.00166 |
Grade A, and why
dough-slice-plan-refinement 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 9d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slice-plan refinement
Refine an existing executable plan in place. Do not create another plan, implement product code, or change its selected story or bounded correction outcome.
Require a refinable plan
Require an existing executable plan and this project's context required by dough-slice-planning, especially any supplied target, hard limit, exceptions, overrun policy, and the plan lifecycle.
Identify whether the plan's source is a selected feature story or a bounded retrospective correction under planning scope and lifecycle. For a complete correction, use its correction input directly from its story and plan, or from a plan-homed correction's plan alone; create no seed. Name whichever required correction field is missing and stop. A complete plan permits refinement, not execution; preserve the invoking instruction's authorization boundary. Before revising boundaries, apply the shared reassessment decision.
- If no plan exists, use
dough-slice-planning. - If a plan is marked as awaiting story refinement after resplitting, use dough-story-refinement on its mapped story and realign the plan before treating it as refinable or executable.
- If the selected story's goal, scope, or examples must change, use dough-story-refinement.
- If a correction's beneficiary, bounded outcome, scope, or proof must change, stop through the shared execution-decision handoff; do not turn it into a feature story. A disputed product constraint uses the plan-conflict handoff below and remains human-owned.
- If the parent problem, candidate selection, or sibling ordering must change, use dough-story-decomposition.
- Treat the plan as
ready for direct executiononly when cumulative design is supported, every boundary preserves useful progress or learning, and all slices are cohesive, single-proof-loop, meet supplied targets, and have no unexplained path beyond a hard limit. Record that outcome through assess readiness at preparation completion when the work item has a recorded identity. Execution still requires separate authorization from the invoking workflow.
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.
- 9d ago Changed · +5 lines 94519a7400b1
- 18d ago Changed · +4 lines 55850f54f767
- 1mo ago Changed · +2 tokens per session 4bb4f224e375
- 1mo ago Changed · +2 lines dfd662bd619d
- 1mo ago Changed · +12 lines · +11 tokens per session 1f0ab6cf5ad5
- 1mo ago Changed · +6 lines 9bc218217f2d
- 1mo ago Changed · +1 lines e83f2e939c99
- 1mo ago Changed · +7 lines 84e68fb5152b
- 1mo ago Changed · +21 lines · +12 tokens per session df4ae71ec262
- 1mo ago First seen · 73 lines · 61 tokens per session scan A 2b9dbd784aac
dough-slice-plan-refinement is a skill published in the GitHub repository nerds-odd-e/doughnut (50 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 1,661 once invoked, about $0.0003 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…