yolo

yolo is a command for Claude Code from Helmi/claude-simone. It costs 0 tokens per session (1,450 once invoked), scanned A, original, MIT.

A work mode for completing open tasks without asking the user questions or waiting for confirmation. It includes rules for handling tests, sensitive files, and database changes.

In plain words
What is it for?
Use it when you want an agent to work through general or sprint-specific tasks independently, run tests, fix common issues, and report the selected mode.
Why use it?
It reduces interruptions when a task can be completed from the available information. Its safeguards define when work should stop instead of making risky changes.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/helmi/claude-simone/yolo
Clone the repo
git clone --depth 1 https://github.com/Helmi/claude-simone

Made for: Claude Code.

Wrote 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.

agentmods badge for yolo

README.md
[![agentmods](https://agentmods.dev/badge/commands/helmi/claude-simone/yolo.svg)](https://agentmods.dev/commands/helmi/claude-simone/yolo)
Your own site
<a href="https://agentmods.dev/commands/helmi/claude-simone/yolo"><img src="https://agentmods.dev/badge/commands/helmi/claude-simone/yolo.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,450 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01450
Opus 5 $0.00000 $0.00725
Sonnet 5 $0.00000 $0.00290
Haiku 4.5 $0.00000 $0.00145

Measured 5d ago against content hash cbdf0b5c9a0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

yolo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • yolo — 100% identical, 0 lines differ
legacy/.claude/commands/simone/yolo.md · 158 lines

How it starts

The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Execute all open tasks in YOLO mode

This mode is meant to be run without user interaction. You DO NOT ask the user any questions or ask for confirmation If in doubt you RESEARCH and ULTRATHINK about the best solution.

IMPORTANT you try not to stop at any certain point but do so if you need after thoughtful consideration.

Priority is to get the work completed.

Mode Selection

Check <$ARGUMENTS>:

  • If sprint ID provided (e.g., S03): Work ONLY on that sprint
  • If empty: Work on general tasks first, then active sprint tasks

Report Mode to the User!

Safety Guidelines

  • NEVER modify critical files (.env, alembic migrations, production configs)
  • STOP if you encounter database schema changes
  • STOP if you need to delete more than 5 files
  • STOP if tests are failing after your changes
  • ALWAYS run tests after implementing a task

Follow this exact process

You need to stick to this process and PRECISELY follow it

Before you start:

  • Run tests to ensure clean baseline using test.md command (@.claude/commands/simone/test.md)

  • If FAIL rate is above 10% asses if a fix is possible. If so, fix and move on. If not, move on anyways.

  • Check git status to ensure clean working directory

  • If git status is not clean just remember and report to the user at the end, but move on.

Also consider <$ARGUMENTS> - if anything between <> can be considered additional instructions, prioritize them in the process.

Get the current datetime stamp from the system and remember it

FIND OPEN WORK

Execute based on mode:

If Sprint ID provided in arguments:

  • Navigate to .simone/03_SPRINTS/{sprint_id}/
  • Check if sprint has tasks (T*.md files)
  • If NO tasks exist:
    • Check for sprint meta file
    • If meta exists: Jump to ### CREATE SPRINT TASKS
    • If no meta: Exit with error - sprint doesn't exist
  • If tasks exist: Continue to Task selection section below

If NO arguments (general mode):

  • Use PARALLEL SUBAGENTS to check:
    • .simone/04_GENERAL_TASKS for open general tasks
    • .simone/00_PROJECT_MANIFEST.md for currently active sprint
    • .simone/03_SPRINTS/ for any sprint with only meta file
  • Priority order:
    1. General tasks (if any open)
    2. Active sprint tasks (if any open)
    3. Sprint needing task creation (if found) - maintain order of Sprints

Read the full file on GitHub · 158 lines

Changes

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.

  1. 5d ago First seen · 158 lines · 0 tokens per session scan A cbdf0b5c9a0b

Subscribe to this mod's changes

yolo is a command published in the GitHub repository Helmi/claude-simone (558 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,450 tokens. 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-30.