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-story-wrap-up/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-story-wrap-up)<a href="https://agentmods.dev/skills/nerds-odd-e/doughnut/dough-story-wrap-up"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-story-wrap-up/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-story-wrap-up"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-story-wrap-up.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.00111 | $0.03205 |
| Opus 5.5 | $0.00044 | $0.01282 |
| Sonnet 5.5 | $0.00022 | $0.00641 |
| Haiku 4.5 | $0.00011 | $0.00320 |
Grade A, and why
dough-story-wrap-up 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 yesterday.
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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story wrap-up
Close one selected feature story, bounded retrospective correction, or contextual
instruction when the coordinator invokes wrap-up explicitly or through Execute
Plan's authorized planned continuation.
That continuation retains the same execution context and publication authority,
including local-only/no-push instructions. Use available execution context and
optional retrospective advice. Leave maintained product knowledge without spent
source or plan history in the current snapshot. Do not invent findings, records,
or another-conversation requirements. With --process-retrospective, also review this wrap-up's process.
Resolve this project's context
Require one selected work identity. Use a canonical story — a feature story, or a correction's minimal story linked to its plan — when it is that work's active home. A plan-homed correction uses its plan when it satisfies the correction-input contract in planning scope and lifecycle; do not require or create a seed for it. When the source is neither a story nor a correction plan, use a contextual instruction with retained execution identity, changes, and proof; do not require or create a story, plan, or queue entry. Name any missing required field, leave the affected work intact, and stop before closure. Do not invent conventions, artifacts, another review, or claim closure.
Resolve from this project, not this skill's location:
- repository root and Git working tree;
- canonical seed location, story identity, heading or stable-anchor conventions for a selected feature story;
- for planned work: executable-plan location, status vocabulary, and the selected work's plan identity;
- for planless work: the supplied story or instruction, its changes, available execution results, and retained execution identity;
- optional retrospective advice when present, including an empty result, and the product advice in the plan's execution-complete record;
- Git commit conventions used to preserve a recoverable revision;
- selected mode, execution checkout and branch, authorized remote and target branch, and an originating or default checkout only when one is available;
- the product backlog path when a Taken or Backlog list entry points at the selected work; and
- shared records that name the selected work: its seed when applicable, process
log (
DearDough.mdunless this project sets another canonical location), incoming links, and assessment records.
What ships with it
8 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.
- references/follow-up-disposition.md 3.4 KB
- references/story-branch-integration.md 3.3 KB
- scripts/trunk-closure-arguments.mjs 1.9 KB runs code
- scripts/trunk-closure-completion.mjs 1.0 KB runs code
- scripts/trunk-closure-observer.mjs 6.0 KB runs code
- scripts/trunk-closure-settlement.mjs 7.6 KB runs code
- scripts/trunk-closure-visit.mjs 4.9 KB runs code
- scripts/trunk-closure.mjs 7.4 KB runs code
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.
- yesterday Changed dfabc90434ee
- 9d ago Changed · -13 tokens per session e82b32feba08
- 14d ago Changed f340164a4e1b
- 18d ago Changed · -22 lines a6d185e11dfd
- 19d ago Changed · +1 lines 3d5b2a0f3539
- 23d ago Changed · +16 lines · +28 tokens per session cea9e93c3b6b
- 26d ago Changed · +16 lines 2217dbab0082
- 27d ago Changed · -9 lines b8702832bc0d
- 1mo ago Changed · -2 lines 45788c5b9b69
- 1mo ago First seen · 251 lines · 96 tokens per session scan A a84d5a8b0c67
dough-story-wrap-up is a skill published in the GitHub repository nerds-odd-e/doughnut (50 stars, last pushed today), licensed MIT. It adds 111 tokens to every session and 3,205 once invoked, about $0.0004 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-11.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.