disable-safe-yolo

disable-safe-yolo is a command for Claude Code from indranildchandra/claude-local-starter. It costs 0 tokens per session (604 once invoked), scanned B, original, MIT.

A repository command that removes the safe-yolo permission entries it previously added from Claude Code settings. It can target a specified repository or detect one from the working directories.

In plain words
What is it for?
Use it to turn off safe-yolo permissions in a repository, clean up its settings file, or preview what would be removed.
Why use it?
It removes shared permission settings without disturbing permissions added manually. A dry run lets you preview the changes first.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: reads .claude/ paths.

Good fit Use it to turn off safe-yolo permissions in a repository, clean up its settings file, or preview what would be removed.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/indranildchandra/claude-local-starter/disable-safe-yolo
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.

Clone the repo
git clone --depth 1 https://github.com/indranildchandra/claude-local-starter

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 disable-safe-yolo

README.md
[![agentmods](https://agentmods.dev/badge/commands/indranildchandra/claude-local-starter/disable-safe-yolo/github.svg)](https://agentmods.dev/commands/indranildchandra/claude-local-starter/disable-safe-yolo)
Your own site
<a href="https://agentmods.dev/commands/indranildchandra/claude-local-starter/disable-safe-yolo"><img src="https://agentmods.dev/badge/commands/indranildchandra/claude-local-starter/disable-safe-yolo/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.

agentmods 80×15 button for disable-safe-yolo

Your own site · 80×15
<a href="https://agentmods.dev/commands/indranildchandra/claude-local-starter/disable-safe-yolo"><img src="https://agentmods.dev/badge/commands/indranildchandra/claude-local-starter/disable-safe-yolo.svg" alt="Reviewed on agentmods" width="80" 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 604 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00604
Opus 5 $0.00000 $0.00302
Sonnet 5 $0.00000 $0.00121
Haiku 4.5 $0.00000 $0.00060

Measured 10d ago against content hash e9ac45edb647, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade B, and why

disable-safe-yolo scanned grade B with 1 finding 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 10d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

`<repo>/.claude/settings.json`. `defaultMode` is only removed if it still matches the value yolo set.
commands/disable-safe-yolo.md · 53 lines

How it starts

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

Disable safe-yolo permissions for a repository.

Removes ONLY the allow/deny entries and defaultMode listed in ~/.claude/claude-safe-yolo-permissions.txt from <repo>/.claude/settings.json. defaultMode is only removed if it still matches the value yolo set. Idempotent — manually added permissions are never touched. If the file becomes empty after removal, it is deleted entirely. Feel free to edit ~/.claude/claude-safe-yolo-permissions.txt as your need evolves.

Example invocations (natural language):

  • /disable-safe-yolo
  • /disable-safe-yolo in the current repo
  • /disable-safe-yolo for your-directory/your-repo
  • /disable-safe-yolo dry run — preview what would be removed without making changes

Step 1 — Determine target directory

Check if the user passed a path or natural language hint in the arguments:

  • If a path is mentioned (e.g. "for /some/path", "in /some/path") → use that path directly, skip to Step 2.
  • If the user says "dry run", "preview", or "show me" → note this for Step 2.
  • Otherwise, auto-detect using this logic:
  1. From your environment context, collect all known working directories (primary + additional).
  2. Filter out non-repo paths — exclude anything under ~/.claude, ~/.claude-work, /tmp, or /var.
  3. Count what remains:
    • Exactly one candidate → announce it and proceed directly to Step 2 (no confirmation yet):

      "The only non-excluded working directory is ."

    • Multiple candidates → list them and ask:

      "Which directory should I disable safe-yolo in?" Wait for reply before continuing.

    • Zero candidates → ask the user to paste the full path.

Step 2 — Show dry-run summary and confirm with user

Run the dry-run to show exactly what permissions would be removed and what would be preserved:

~/.claude/disable-safe-yolo.sh --dry-run --dir="<RESOLVED_DIR>"

Then ask the user directly in the conversation:

"Safe-yolo will be disabled in <RESOLVED_DIR>. Does this directory look correct and do you want to proceed? (y/n)"

Read the full file on GitHub · 53 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. 10d ago First seen · 53 lines · 0 tokens per session scan B e9ac45edb647

Subscribe to this mod's changes

disable-safe-yolo is a command published in the GitHub repository indranildchandra/claude-local-starter (13 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 604 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.