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-statusgit 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-status)<a href="https://agentmods.dev/skills/corichui/yolo/yolo-status"><img src="https://agentmods.dev/badge/skills/corichui/yolo/yolo-status/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-status"><img src="https://agentmods.dev/badge/skills/corichui/yolo/yolo-status.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.00047 | $0.00669 |
| Opus 5.5 | $0.00019 | $0.00268 |
| Sonnet 5.5 | $0.00009 | $0.00134 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
yolo-status 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 — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
yolo-status
Report the state of all features by DERIVING it from git (.claude/yolo/conventions.md). There is no stored status field — do not look for one.
Procedure
- Resolve
base_branch(workspace/config.yamlproject.base_branch, else the detection rule in.claude/yolo/conventions.md). Guard every ref withgit rev-parse --verify -qbefore using it; ifbase_branchdoes not resolve, report a config error and stop. Ifworkspace/config.yamlis absent, use the config-absent fallback from conventions. - Enumerate live branches once —
git for-each-ref --format='%(refname:short)' refs/heads/feature/— so afeature/<slug>with no brief is surfaced as anuntracked-branchrow, not silently dropped. - For each
workspace/features/*/brief.md, take<slug>from the folder. A brief with front-mattercancelled: trueis reported as cancelled and otherwise skipped. Else derive status exactly per.claude/yolo/conventions.mdDeriving status, in order:- done — ANY of (first match wins): tag
yolo/done/<slug>exists, OR base history carries aYOLO-Feature: <slug>trailer (both durable — survive branch deletion/squash), OR (branch still present) its tip carriesYOLO-Verified: truewith a committedverification.md. This is what makes a shipped-and-deleted branch read as done, not planned. (git branch --mergedis intentionally not used — it false-positives an empty freshly-cut branch.) - in-progress —
feature/<slug>exists and is not done. Completed tasks (advisory, deduped):git log <base>..feature/<slug> --format='%(trailers:key=YOLO-Task,valueonly)' | sed '/^$/d' | sort -u(count vs the task total inplan.md— progress only, never the done test). - planned — brief exists, no done-evidence, and
feature/<slug>does not exist.
- done — ANY of (first match wins): tag
- Group rows by the brief's
milestone:value when set. Forplanned/in-progressrows whose brief listsdepends_on, flag any dependency not yetdoneasblocked-by: <slug>. - Print a compact table: slug · status · tasks(done/total, for in-progress) · milestone · blocked-by. Add a one-line resume hint from the most recent in-progress branch's last commit subject (e.g. "resume with yolo-feature ").
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 · 26 lines · 47 tokens per session scan A af5b92ed5cc2
yolo-status is a skill published in the GitHub repository CoriChui/yolo (9 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 669 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
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.
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.
task-board-setup
Creates a Codex file-based task board. Explicit user invocation only.
convention-setup
Installs project conventions and reversible loading guidance; extracts representative implementations, patterns, architecture, and accepted rules. Triggers: convention setup, extract conventions, etalon classes.