Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add kazuph/yunomi --skill donegit clone --depth 1 https://github.com/kazuph/yunomiWrote 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/kazuph/yunomi/done)<a href="https://agentmods.dev/skills/kazuph/yunomi/done"><img src="https://agentmods.dev/badge/skills/kazuph/yunomi/done/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/kazuph/yunomi/done"><img src="https://agentmods.dev/badge/skills/kazuph/yunomi/done.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.00027 | $0.03181 |
| Opus 5.5 | $0.00011 | $0.01272 |
| Sonnet 5.5 | $0.00005 | $0.00636 |
| Haiku 4.5 | $0.00003 | $0.00318 |
Grade A, and why
done scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
For backend/fullstack, run the real test framework against the actual database or permitted local emulator and generate its coverage report (using its supported coverage option); curl or manual API calls do not replace t How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complete and prove the work
Canonical source: kazuph/yunomi, plugin/skills/done/. Personal skill directories contain identical copies, distributed together with /do and /bucho.
Use after /do, after a /bucho implementation lead finishes its work, or when the user requests completion of an existing task. There is one completion standard, with no tiny/full or evidence-only choice. Required checks follow the actual requirements, affected behavior, and repository rules.
Recover the original request, corrections, decisions, worktree, diff, tests, and evidence. If a piece is missing, inspect the real state rather than guessing or restarting the task from scratch. Do not silently change the request to fit the implementation.
Read the adjacent /do verification contract. Resolve and read the applicable review-code-security, review-e2e, review-ui-ux, report-builder, and report-validator instruction files from the trusted Yunomi plugin/checkout, plus the installed testing, artifact-proof, validate-report, and yunomi skills. Record exact paths. A name in a prompt is not a completed review; missing required instructions/capability must be restored from an authorized local source or reported as a blocker, never silently skipped or downloaded as a new runner. Apply checklists without executing legacy secret-printing commands or violating the current read-only reviewer policy.
For standalone /done as well as a /do handoff, read the applicable webapp-impl, backend-impl, or mobile-impl checklist and, for Web UI, frontend-design. Verify the inherited implementation/design requirements, including reduced-motion preferences, against the existing user design system and current policy.
Inherit the selected procedure
Recover the playbook name and exact path from /do, or classify a standalone completion the same way /do would. Do not reclassify unless the remaining work is a different kind of request. Then verify that playbook's completion condition:
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 · 120 lines · 27 tokens per session scan A 0ceb8ac8c23e
done is a skill published in the GitHub repository kazuph/yunomi (21 stars, last pushed 23d ago), licensed MIT. It adds 27 tokens to every session and 3,181 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-17.
Other skills, from other repositories
development-estimation
Use when estimating time, effort, cost, or complexity for features, projects, refactors, and bug backlogs. Produces defensible estimates via triage, decomposition, risk handling, and confidence intervals, with clear assumptions and validation steps.
tech-debt
Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register.
pr-review-triage
Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
maintain
Triage and work through Ouroboros GitHub issues and pull requests as a maintainer. Use for ooo maintain, backlog cleanup, review, merge readiness, duplicate PRs, and issue disposition.