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-roadmapgit 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-roadmap)<a href="https://agentmods.dev/skills/corichui/yolo/yolo-roadmap"><img src="https://agentmods.dev/badge/skills/corichui/yolo/yolo-roadmap/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-roadmap"><img src="https://agentmods.dev/badge/skills/corichui/yolo/yolo-roadmap.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.00070 | $0.00390 |
| Opus 5.5 | $0.00028 | $0.00156 |
| Sonnet 5.5 | $0.00014 | $0.00078 |
| Haiku 4.5 | $0.00007 | $0.00039 |
Grade A, and why
yolo-roadmap 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.
What it actually says
yolo-roadmap
Turn one big goal into several atomic feature briefs. There is no "release" container — just briefs, optionally tagged with a shared milestone.
Procedure
- Clarify the big goal and its boundary (what's out of scope). Optionally invoke yolo-research for codebase context.
- Decompose into independent features, each shippable on its own. Note any cross-feature
depends_on(honored by the model; there is no DAG machine). - For each feature, draft
workspace/features/<slug>/brief.mdfrom.claude/yolo/templates/brief.md— setgoal,success_criteria, and a sharedmilestone:value if they ship as a set. - Present the proposed feature list for approval BEFORE creating the briefs — the plan-gate analogue for a roadmap; no billed code work happens here (
.claude/yolo/conventions.mdThe two gates). Skip only if the user pre-consented. - On approval, write and commit each brief (
yolo: brief <slug>). Each is later picked up by yolo-feature.
Constraints
- You only create briefs (status "planned"). You do not branch, plan, or execute — that is yolo-feature, per feature.
- No container, no lifecycle, no status field. Grouping is the
milestone:label only. - Run decomposition/analysis at the
agents.roadmaptier fromworkspace/config.yaml.
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 · 21 lines · 70 tokens per session scan A 8c9c0b33d0a4
yolo-roadmap is a skill published in the GitHub repository CoriChui/yolo (9 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 390 once invoked, about $0.0003 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.