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/dentiny/kon/yolo-modenpx skills add dentiny/kon --skill yolo-modegit clone --depth 1 https://github.com/dentiny/konWrote 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/dentiny/kon/yolo-mode)<a href="https://agentmods.dev/skills/dentiny/kon/yolo-mode"><img src="https://agentmods.dev/badge/skills/dentiny/kon/yolo-mode.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 | $0.00049 | $0.00919 |
| Opus 5 | $0.00024 | $0.00460 |
| Sonnet 5 | $0.00010 | $0.00184 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
yolo-mode 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YOLO Mode
Owner: orchestrator
Consumers: any /kon:* command when the --yolo flag is present
Core principles (always): follow skills/core-principles — YOLO does not waive first principles or simplicity; it only skips confirmation checkpoints.
The user set the task and stepped away. Run it. Don't interrupt them for anything that has a reasonable default or can be retried automatically.
What changes in YOLO mode
| Normal checkpoint | YOLO behavior |
|---|---|
| Wait for user to confirm Mugi's plan | Still required — wait-for-user --after plan |
| Pre-plan understanding gate (before Mugi) | Still required — ask questions per skills/pre-plan-gate; do not spawn Mugi until ready |
| Wait after each milestone Mio-approved | Still required — wait-for-user --after milestone --milestone N |
| Auto-accept decisions within the plan | Auto-accept all [**default**] decisions in Mugi's ## Decisions needed |
| Ask user when a plan step is ambiguous | If plan has [**default**], use it; otherwise STOP and ask — never invent |
| Notify user when Mio blocks | Auto-send must-fix list back to Yui; retry silently |
| Per-agent step summary to user | Suppress — only report at the end (or when stopping) |
Auto-accepted decisions and auto-retries are recorded in the session log
(see skills/session-tracking) so the user can review what happened.
YOLO auto-accepts plan defaults and retries failures — it does not permit guessing unclear requirements. See skills/ask-dont-guess.
When to STOP and ask the user — always, even in YOLO mode
-
Pre-plan gate — After Azusa (and debug notes if applicable), always run
skills/pre-plan-gatebefore Mugi. YOLO does not skip understanding questions. -
Plan confirmation — After Mugi finishes, always
wait-for-user --after planbefore Yui. YOLO only auto-accepts decisions within the approved plan.
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 · 79 lines · 49 tokens per session scan A f83884838c38
yolo-mode is a skill published in the GitHub repository dentiny/kon (3 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 919 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…