yolo

yolo is a skill for Claude Code, Codex from jgamaraalv/ts-dev-kit. It costs 96 tokens per session (3,555 once invoked), scanned C, original, MIT.

A setup tool for running Claude Code inside a Docker development container with permission prompts disabled. The container isolates the work from the rest of the computer, but Claude can access anything placed inside it, including mounted credentials.

In plain words
What is it for?
Setting up a devcontainer, checking whether Docker and VS Code are available, and launching Claude Code in autonomous mode.
Why use it?
It removes repeated approval prompts during unattended coding while adding isolation around the project. It still carries security risks and should be used only with trusted repositories.

Skill for Claude CodeCodex

Part of the ts-dev-kit plugin — 22 skills, 15 agents shipped together

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 skills/jgamaraalv/ts-dev-kit/yolo
Any agent
npx skills add jgamaraalv/ts-dev-kit --skill yolo
Clone the repo
git clone --depth 1 https://github.com/jgamaraalv/ts-dev-kit

Made for: Claude Code, Codex.

Or install ts-dev-kit, the plugin that ships this one along with the rest of its 22 skills, 15 agents.

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/skills/jgamaraalv/ts-dev-kit/yolo.svg)](https://agentmods.dev/skills/jgamaraalv/ts-dev-kit/yolo)
Your own site
<a href="https://agentmods.dev/skills/jgamaraalv/ts-dev-kit/yolo"><img src="https://agentmods.dev/badge/skills/jgamaraalv/ts-dev-kit/yolo.svg" alt="Measured on agentmods" height="20"></a>
Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,555 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 3 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.00096 $0.03555
Opus 5 $0.00048 $0.01777
Sonnet 5 $0.00019 $0.00711
Haiku 4.5 $0.00010 $0.00356

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

Security

Grade C, and why

yolo scanned grade C with 3 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 4d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo systemctl start docker

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

ls .claude/skills/*/SKILL.md 2>/dev/null && echo "SKILLS_PRESENT" || echo "SKILLS_MISSING"

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

> **Security trade-off:** `--dangerously-skip-permissions` means Claude can execute ANY command inside the container without asking. The firewall and container isolation are your safety net. Only use this with trusted co
skills/yolo/SKILL.md · 427 lines

How it starts

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

<live_context> Project root: !pwd

Devcontainer present: !ls -la .devcontainer/devcontainer.json 2>/dev/null && echo "YES" || echo "NO"

Docker daemon status: !docker info --format '{{.ServerVersion}}' 2>/dev/null && echo "RUNNING" || echo "NOT RUNNING"

Docker Desktop installed: !command -v docker 2>/dev/null || echo "NOT FOUND"

VS Code installed: !command -v code 2>/dev/null || echo "NOT FOUND" </live_context>

<trigger_examples>

  • "yolo"
  • "Enter yolo mode"
  • "Set up a devcontainer so Claude can run autonomously"
  • "I want to run Claude Code without permission prompts"
  • "Skip permissions safely with a devcontainer"
  • "Set up autonomous mode" </trigger_examples>

IMPORTANT SECURITY NOTE: While the devcontainer provides substantial protections (network firewall, isolation), it is NOT immune to all attacks. Only use devcontainers with trusted repositories. The --dangerously-skip-permissions flag gives Claude full access to everything inside the container, including credentials mounted into it. Always inform the user of this trade-off.

START
  │
  ├─ Phase 1: Detect devcontainer
  │    ├─ EXISTS → Phase 1.5
  │    └─ MISSING → Phase 5 (install) → Phase 1.5
  │
  ├─ Phase 1.5: Ensure plugin availability
  │    └─ Copy agents/skills/agent-memory into project if missing → Phase 2
  │
  ├─ Phase 2: Check Docker
  │    ├─ RUNNING → Phase 3
  │    └─ NOT RUNNING → Phase 4 (start Docker) → Phase 3
  │
  ├─ Phase 3: Launch devcontainer
  │    └─ claude --dangerously-skip-permissions
  │
  ├─ Phase 4: Start Docker
  │    └─ Start Docker Desktop/daemon → Phase 3
  │
  └─ Phase 5: Install devcontainer
       └─ Scaffold .devcontainer/ → Phase 1.5

<phase_1_detect>

Phase 1 — Detect devcontainer

Check whether .devcontainer/devcontainer.json exists in the project root.

  1. Read the <live_context> above for the pre-injected detection result.
  2. If YES — announce to the user and proceed to Phase 1.5:

DEVCONTAINER DETECTED.devcontainer/ found. Checking plugin availability...

  1. If NO — announce and proceed to Phase 5:

NO DEVCONTAINER FOUND — I'll set one up using the Claude Code reference implementation.

</phase_1_detect>

<phase_1_5_ensure_plugin>

Read the full file on GitHub · 427 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 4d ago First seen · 427 lines · 96 tokens per session scan C 5cd6625882e3

Subscribe to this mod's changes

yolo is a skill published in the GitHub repository jgamaraalv/ts-dev-kit (15 stars, last pushed 6mo ago), licensed MIT. It adds 96 tokens to every session and 3,555 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 3 findings (asks for root, enumerates other installed skills, unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

deploy-docker-compose

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…

omnigent-ai/omnigent · 84 tokens

compute-env-setup

Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.

companion-inc/feynman · 45 tokens

securing-kubernetes-on-cloud

This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…

xalgorix/xalgorix · 80 tokens

detecting-privilege-escalation-in-kubernetes-pods

Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.

xalgorix/xalgorix · 40 tokens

implementing-rbac-hardening-for-kubernetes

Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.

xalgorix/xalgorix · 41 tokens

release-rome-image

Release a new Rome runtime image by pushing a vX.Y.Z tag — pick the version, verify main is releasable, push the tag, and confirm the image published to Docker Hub. Covers the v runtime-image tag only, not the desktop app (desktop-v) and not npm packages (ui-v, app-runtime-v).

rome-os/rome · 81 tokens