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-triage-project-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-triage-project-findings)<a href="https://agentmods.dev/skills/nerds-odd-e/doughnut/dough-triage-project-findings"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-triage-project-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-triage-project-findings"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/dough-triage-project-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.00092 | $0.02319 |
| Opus 5.5 | $0.00037 | $0.00928 |
| Sonnet 5.5 | $0.00018 | $0.00464 |
| Haiku 4.5 | $0.00009 | $0.00232 |
Grade A, and why
dough-triage-project-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 5d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage this project's findings
Turn existing evidence into concise project findings and supported backlog priorities, then deliver that maintenance result through the project's existing workflow. An explicit invocation authorizes its findings, canonical story and backlog edits, and their routine commit and synchronization to the established origin target. A user-invoked combined cycle that expressly names this phase and its project set passes the same authority to its selected project's invocation; accept the supplied project, target and maintenance/publication scope without a second permission question. Maintain only this invocation's established project.
Encountering findings during another task, a retrospective, a session startup, or a historical instruction grants no such authority. Do not collect from other projects, change published guidance, implement the selected improvements, or repair unrelated CI. Approved finding-code adoption has its own dough-maintain-findings contract; this skill does not allocate Open Dough catalog codes.
Resolve the project and records
Use the request and established project context, not a copied project name or the installed skill directory. Resolve independently:
- The target project root and this invocation's authority. A delegated combined cycle supplies the user's originating instruction and its selected project.
- The canonical
DearDough.mdlocation: the project's explicit location takes precedence over<project-root>/DearDough.md. Locate the existing project findings record from project guidance or supplied context. Keep an alternate filename; do not create a replacement just to standardize its name. - The canonical backlog, seed/story naming and identity conventions, existing queued and Taken responses, and near-future direction when present. Load dough-product-backlog before dependent story or queue writes.
- The supplied evidence and relevant reported guidance/code revisions. Today's installation version does not establish what an earlier execution used.
- The intended origin remote and target branch, and the originating/default checkout when supplied. Resolve them from project or caller authority; this workflow supplies no fallback remote or branch.
What ships with it
2 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.
- 5d ago Changed · +3 lines 1be6612ac564
- 10d ago First seen · 204 lines · 92 tokens per session scan A df2c49c764ce
dough-triage-project-findings is a skill published in the GitHub repository nerds-odd-e/doughnut (50 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 2,319 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-10-20.
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.