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 dogit 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/do)<a href="https://agentmods.dev/skills/kazuph/yunomi/do"><img src="https://agentmods.dev/badge/skills/kazuph/yunomi/do/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/do"><img src="https://agentmods.dev/badge/skills/kazuph/yunomi/do.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.00022 | $0.03399 |
| Opus 5.5 | $0.00009 | $0.01360 |
| Sonnet 5.5 | $0.00004 | $0.00680 |
| Haiku 4.5 | $0.00002 | $0.00340 |
Grade A, and why
do 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Own the requested outcome
Canonical source: kazuph/yunomi, plugin/skills/do/. Personal skill directories contain identical distribution copies. Maintain /do, /done, and /bucho together; edit the Yunomi source first.
Use this entry for a new task or to resume one. Keep the same lead responsible through /done; the user does not select a tiny/full mode or request the completion phase separately. For explicit delegated execution, use /bucho, which assigns this same workflow to an implementation lead.
Read the current task, repository instructions, and existing task state first. User requirements and environment policies take precedence over this skill. Keep the requested behavior, architecture, quality, and scope intact; never offer or deliver a reduced version to save time, cost, or tokens.
Select the matching procedure
Before planning work, classify the request and read the matching file next to this skill. Record the chosen name and the exact path. These files are not slash commands; do not add /investigation or similar entries.
| Request | Read |
|---|---|
| Explain how something works, why it exists, or which option is safer, with a cited answer rather than a code change | playbooks/investigation.md |
| A reported defect to reproduce and fix | playbooks/bug-fix.md |
| New or changed observable behavior | playbooks/feature.md |
| Structure or placement change that must keep behavior | playbooks/refactoring.md |
| Measured slowness | playbooks/perf-issue.md |
| Create or change a skill, playbook, or distributed agent instruction | playbooks/authoring-a-skill.md |
| Resume an in-flight task from an existing record or worktree | playbooks/session-pickup.md |
| None of the above | Write the procedure first in the task record. Do not start implementation until that procedure exists. |
Resolve paths relative to this SKILL.md. Investigation is read-only and skips later implementation sections until a different playbook is selected. Other playbooks then continue with the rest of this skill. Hand the chosen name and path to /done and, when delegating, to /bucho.
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.
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 · 133 lines · 22 tokens per session scan A f826be125c09
do is a skill published in the GitHub repository kazuph/yunomi (21 stars, last pushed 23d ago), licensed MIT. It adds 22 tokens to every session and 3,399 once invoked, about $0.0001 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-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.