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 CoriChui/yolo --skill yolo-nextgit clone --depth 1 https://github.com/CoriChui/yoloWrote 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/corichui/yolo/yolo-next)<a href="https://agentmods.dev/skills/corichui/yolo/yolo-next"><img src="https://agentmods.dev/badge/skills/corichui/yolo/yolo-next/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/corichui/yolo/yolo-next"><img src="https://agentmods.dev/badge/skills/corichui/yolo/yolo-next.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.00088 | $0.00698 |
| Opus 5.5 | $0.00035 | $0.00279 |
| Sonnet 5.5 | $0.00018 | $0.00140 |
| Haiku 4.5 | $0.00009 | $0.00070 |
Grade A, and why
yolo-next 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 2d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
yolo-next
Recommend what to do next. Read-only: it never writes briefs, branches or commits. Status
rules: ../../yolo/conventions.md.
Gather
- Derive every feature's status exactly as
yolo-statusdoes (landed, verified, in-progress, planned, cancelled, untracked-branch). Read each active brief'sgoal,milestoneanddepends_on. - For in-progress branches, note the last commit date:
git log -1 --format=%cr feature/<slug>. - Count dependents: how many planned or in-progress briefs list each slug in
depends_on. - Open issues, if a forge CLI is available and authenticated:
gh issue list --limit 20orglab issue list --per-page 20. Skip quietly otherwise. - Code markers:
git grep -nE 'TODO|FIXME|HACK'on base, counted per file. Mention only clusters, not every line.
Rank
Apply these in order. Each rule only reorders within what the earlier rules left open.
- Finish before starting. A
verifiedfeature is one merge from done; it goes first. - Continue live work. An in-progress branch touched in the last 7 days beats starting something new. With 3 or more in progress, recommend only finishing or cancelling, not starting.
- Decide on stalled work. In-progress with no commits for 7+ days: recommend
continuing it or cancelling it (
yolo-briefcancel). Don't let it sit silently. - Unblock others. Among unblocked planned briefs, prefer the one with the most
dependents, then the current milestone (the one with the most features already landed),
then the oldest
created_at. - Outside signals. Bug issues and TODO clusters are candidates for non-feature work. Suggest them as plain fixes, not briefs, unless one is clearly a feature.
- Untracked branches. Flag them: brief them or delete them.
Output
The top 3, each with:
- what: slug or issue, and one line on what it is
- why now: the rule that ranked it, in plain words
- unblocks: dependents, if any
- next step: the exact command or prompt, e.g.
git switch feature/<slug>, "verify ", "merge feature/", "brainstorm ", "cancel "
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.
- 2d ago First seen · 51 lines · 88 tokens per session scan A 28ade1c7dbe9
yolo-next is a skill published in the GitHub repository CoriChui/yolo (9 stars, last pushed 2d ago), licensed MIT. It adds 88 tokens to every session and 698 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-26.
Other skills, from other repositories
tackle-issue
Start-of-work triage in this monorepo. Trigger on: a GitHub issue number ("tackle issue 99", "work on #42", bare #N), pasted proposal/spec text ("investigate this", "pressure-test this", "scope this"), or picker phrasing ("tackle the next issue", "what should I work on"). Read-only investigation that tries to falsify…
hermit-scribe
File a GitHub issue or post a comment on an existing issue via a GitHub App bot identity. Use when the operator says "file as a GH issue", "open an issue for PROP-NNN", "report this to the tracker", "add a comment to issue.
stale-proposals
Audit this repository's local proposal queue for stale entries: proposals still marked proposed, deferred, or accepted even though the work already shipped, plus old proposals whose subject has become inert. Reconcile proposals against plugin changelogs and first-parent Git history, automatically resolve only…
atlas-present
Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".
crest-narrative
Strategic narrative — write a standalone strategy memo that frames product direction, bets, and rationale for a planning horizon. Use when asked to "write a strategy doc", "product vision", "strategic narrative", "company strategy memo", "planning memo", or "explain our product direction".
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.