Borrowing it
Nothing to install: this file belongs to CoriChui/yolo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CoriChui/yolo/main/CLAUDE.mdgit 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/instructions/corichui/yolo/claude-md)<a href="https://agentmods.dev/instructions/corichui/yolo/claude-md"><img src="https://agentmods.dev/badge/instructions/corichui/yolo/claude-md/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/instructions/corichui/yolo/claude-md"><img src="https://agentmods.dev/badge/instructions/corichui/yolo/claude-md.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.01090 | $0.01090 |
| Opus 5.5 | $0.00436 | $0.00436 |
| Sonnet 5.5 | $0.00218 | $0.00218 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
yolo CLAUDE.md 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YOLO workflow (this is a YOLO-initialized repo)
This project uses YOLO (reasoning-first). Feature state lives in git, not in tracked
status files — see .claude/yolo/conventions.md. This block is the primary human-readable
routing guide; the machine auto-triggers live in each skill's description. The confidence
tiers and does-NOT-route taxonomy below are unique to this block.
File resolution: YOLO may be installed as a plugin. If
${CLAUDE_PLUGIN_ROOT}is set, resolve framework paths (.claude/yolo/...,.claude/skills/...) against it; otherwise read them project-relative. Project state (workspace/, thisCLAUDE.md) is always project-local. See Where YOLO's files live inconventions.md.
Routing feature intent (auto-detect, then confirm at the gates)
When a prompt expresses intent to build / add / implement / create a feature, route it to
the yolo-feature skill on your own — don't wait to be told "use YOLO." For feature intent
this takes precedence over generic brainstorming. Auto-routing is safe because the cheap
phase (intent capture + brief) is reversible and the plan gate stops before any expensive or
irreversible work, so a wrong guess costs at most a throwaway brief.
Routes to yolo-feature (feature intent):
"add CSV export", "build a settings page", "implement OAuth login", "create an endpoint for
X", "support dark mode", "let users reset their password".
Does NOT route — handle normally (the common false positives):
- Questions / understanding — "how does X work?", "where is Y?", "why does Z happen?".
Answer directly; reach for
yolo-researchonly if deeper code exploration helps. - Trivial edits — a typo, a one-line or single-file fix, a rename, a config tweak. Below the ceremony threshold: just make the edit, no brief.
- Refactors / cleanups with no new user-facing capability — do them directly unless the user explicitly wants it tracked as a feature.
- Bug reports — "X is broken", "fix the 500 on login" → route to
yolo-debugfor a systematic reproduce → isolate → fix → verify pass (a genuinely trivial one-line fix can still just be made). If the fix turns out to need new capability,yolo-debughands off toyolo-feature. - Other YOLO acts — decisions, status, intake, roadmap (see Other intents).
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 · 69 lines · 1,090 tokens per session scan A 2fedc5e21895
yolo CLAUDE.md is an instructions file published in the GitHub repository CoriChui/yolo (9 stars, last pushed 3mo ago), licensed MIT. It adds 1,090 tokens to every session, about $0.0044 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).