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 agentmods add skills/corichui/yolo/yolo-roadmapnpx 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.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.00195 |
| Sonnet 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 5d 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.
- 5d 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 2mo ago), licensed MIT. It adds 70 tokens to every session and 390 once invoked, about $0.0003 per session on Opus 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
create-kr-patch
Use for Korean (Hangul) fan translations of retro console or PC games, including ROM or disc analysis, text-engine reverse engineering, Hangul fonts and custom encodings, script extraction and reinsertion, code hooks, reproducible product builds, and emulator verification. Apply it to new investigations and follow-up…
0xarchive
Query historical and real-time crypto market data from 0xArchive across two top-level venue APIs: Hyperliquid and Lighter.xyz. HIP-3 builder perps live under the Hyperliquid namespace at /v1/hyperliquid/hip3. HIP-4 outcome markets (binary prediction markets like 'Will BTC be >= X by date Y?') live at…
make-brief
Produce a local HTML page a human can actually read and decide from - a narrative decision brief, an item-by-item technical review page, or a mechanism explainer that walks through a system and its terminology. Triggers when the user says "write this up as an HTML page for me", "I don't follow, give me the full…
quiz-me
Quiz the user on root cause and intended fix BEFORE writing any non-trivial code, then verify comprehension of every change after. Use when the user asks for a bug fix, refactor, or feature and wants to stay technically sharp instead of vibe-coding. Also use when the user says "quiz me", "don't let me vibe code", or…
kimchi
Turn a raw product idea into build-ready docs — one doc per EPIC with locked decisions, exact API contracts, a story-by-story priority plan, and an execute.md handoff Claude can build from across sessions. Gets the clarity by interrogating the user through a roster of expert personas that grill, counter, and refuse to…
slopmop
Trigger when you would normally reach for pytest, gh, mypy, black, or other raw repo tooling. Redirect to sm swab, sm scour, sm buff, sm sail, sm refit, or sm doctor so remediation follows the established rails. Also trigger when asked to "install" or "set up" slop-mop in a repo, or when you find a repo with sm…