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-maintain-findings/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-maintain-findings)<a href="https://agentmods.dev/skills/nerds-odd-e/doughnut/dough-maintain-findings"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-maintain-findings/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-maintain-findings"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-maintain-findings.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.00077 | $0.00990 |
| Opus 5.5 | $0.00031 | $0.00396 |
| Sonnet 5.5 | $0.00015 | $0.00198 |
| Haiku 4.5 | $0.00008 | $0.00099 |
Grade A, and why
dough-maintain-findings 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain finding names
Adopt approved finding names only when the user explicitly invokes this skill
or requests that maintenance. Do not run adoption as a side effect of a
retrospective, reconciliation recommendation, or other work. This increment
supports supplied DD-NNN → ODF-NNN mappings only; do not allocate codes,
reconcile names, merge findings, change statuses, or remove log content.
Recover the request
Resolve the target project, approved mappings, and their concrete finding meaning from the request and established session context. An explicit request to adopt supplied recommendations is sufficient approval; do not ask again when the user has already accepted them. An invocation alone does not approve unaccepted recommendations. If mappings or approval are missing, identify the missing input and make no rename.
Use this project's canonical DearDough.md: an explicitly established location
takes precedence over <project-root>/DearDough.md. Do not infer the project
from the installed skill directory, search other projects, or require a naming
catalog. If the target or canonical location is ambiguous, or the log is missing
or unreadable, explain the limitation and make no write. Do not create a log.
Check each mapping
Read the log and evaluate all approved mappings before editing. Match identity and concrete meaning, not just a similar title or symptom. A source code must identify one finding in this project, and the supplied recommendation's meaning must agree with that finding. Do not infer approval or meaning for another project's same-numbered code.
- Ready: One matching
DD-NNNheading exists and the destinationODF-NNNis unassigned to any other finding. - Already adopted: The matching
ODF-NNNheading and its former-code alias identify this same mapping, with no competing source identity. Leave it unchanged; do not add another alias or finding. - Blocked: The source identity is missing or ambiguous, meaning is missing or mismatched, the destination belongs to another finding, or the requested mappings conflict with each other. Cite the conflicting codes and relevant log or recommendation text. Leave those findings unchanged and the identity decision with the user; do not merge, overwrite, or reinterpret the mapping.
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 · 90 lines · 77 tokens per session scan A e92e771da375
dough-maintain-findings is a skill published in the GitHub repository nerds-odd-e/doughnut (50 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 990 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-13.
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.