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 buchogit 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/bucho)<a href="https://agentmods.dev/skills/kazuph/yunomi/bucho"><img src="https://agentmods.dev/badge/skills/kazuph/yunomi/bucho/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/bucho"><img src="https://agentmods.dev/badge/skills/kazuph/yunomi/bucho.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.00028 | $0.01795 |
| Opus 5.5 | $0.00011 | $0.00718 |
| Sonnet 5.5 | $0.00006 | $0.00359 |
| Haiku 4.5 | $0.00003 | $0.00179 |
Grade A, and why
bucho 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Own the outcome through delegation
Canonical source: kazuph/yunomi, plugin/skills/bucho/. Distribute it unchanged together with /do and /done; do not maintain another personal workflow.
Use when the user explicitly chooses delegated execution. /bucho changes who implements; it does not change the requirements or create another quality level. The implementation lead follows /do through /done, including existing-code reuse, behavior-preserving deslop, real verification, and human review.
Read the current user request, environment policy, and the /do and /done skills. Preserve every requested behavior, architecture constraint, quality requirement, and side-effect boundary. Do not install or execute pstack, ponytail, or other third-party workflow scripts.
Include the diagram in delegation and acceptance
When the outcome includes a yunomi report, require an embedded explanatory diagram in the lead's deliverables and specify the agreed report/asset paths. For a change to an existing workflow, require side-by-side old/new flows with labeled colors for what stays and what changes. The diagram must retain existing functionality, security review, verification, and human approval where applicable.
The manager checks the source-based comparison, actual diagram file, report embedding, and proof that the image loaded in yunomi. A completion summary, text-only report, screenshot, or before/after code is not a substitute. Return missing or unverified diagrams to the same lead; do not hand a diagram-free report to the human. Follow the current image-generation and user-only regeneration policies.
Establish ownership before launch
Carry the pre-change functionality and mandatory review/completion conditions from /do into the delegated acceptance criteria, separately from the new requirements. Inspect the /done regression results and every retained review responsibility yourself. A delegate completing the new feature does not excuse a removed existing feature, missing security review, or unresolved Critical/High finding. Restore task-introduced regressions before human acceptance.
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 · 73 lines · 28 tokens per session scan A 84c708be0d3d
bucho is a skill published in the GitHub repository kazuph/yunomi (21 stars, last pushed 23d ago), licensed MIT. It adds 28 tokens to every session and 1,795 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.