yolobox-orchestrator

yolobox-orchestrator is a skill for Codex from finbarr/yolobox. It costs 65 tokens per session (494 once invoked), scanned A, original, MIT.

A guide for starting and managing Yolobox sessions from outside a Yolobox environment. Yolobox provides isolated workspaces for running coding agents.

In plain words
What is it for?
Starting, inspecting, or controlling Yolobox sessions; checking merged settings; and choosing scratch, read-only, Docker, or network access options.
Why use it?
It helps choose safe session settings without guessing which command or option is needed. It also explains how configuration defaults affect a launch.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Starting, inspecting, or controlling Yolobox sessions; checking merged settings; and choosing scratch, read-only, Docker, or network access options.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/finbarr/yolobox/yolobox-orchestrator
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.

Any agent
npx skills add finbarr/yolobox --skill yolobox-orchestrator
Clone the repo
git clone --depth 1 https://github.com/finbarr/yolobox

Made for: Codex.

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 yolobox-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/skills/finbarr/yolobox/yolobox-orchestrator/github.svg)](https://agentmods.dev/skills/finbarr/yolobox/yolobox-orchestrator)
Your own site
<a href="https://agentmods.dev/skills/finbarr/yolobox/yolobox-orchestrator"><img src="https://agentmods.dev/badge/skills/finbarr/yolobox/yolobox-orchestrator/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 yolobox-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/skills/finbarr/yolobox/yolobox-orchestrator"><img src="https://agentmods.dev/badge/skills/finbarr/yolobox/yolobox-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 494 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00065 $0.00494
Opus 5 $0.00032 $0.00247
Sonnet 5 $0.00013 $0.00099
Haiku 4.5 $0.00006 $0.00049

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

Security

Grade A, and why

yolobox-orchestrator 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 12d 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.

skills/yolobox-orchestrator/SKILL.md · 27 lines

What it actually says

Yolobox Orchestrator

Use this skill for host-side orchestration of yolobox sessions.

Do not use it for questions about the current environment from inside a running box. Inside the container, use yolobox instead.

  1. Start from the user's intent, then choose the smallest yolobox command or flag set that accomplishes it.
  2. Check yolobox config when defaults, merged config, or flag precedence matter.
    • If default_harness is set, bare yolobox launches that shortcut; use yolobox shell for an explicit shell.
  3. Prefer explicit isolation and safety flags:
    • --scratch for disposable or concurrent sessions that must not share /home/yolo.
    • --readonly-project when the agent only needs read access to the project tree.
    • --no-env-passthrough when host API/token environment variables should not enter the box automatically.
    • --claude-config --no-claude-auth when host Claude settings should be synced but the persistent box must keep its own /login credentials. This still live-mounts host Claude project history read/write.
    • --open-bridge only when the agent needs to open HTTP(S) URLs in the host browser.
    • --docker only when the agent needs Docker access or sibling containers.
  4. When you need exact command patterns or edge-case reminders, read references/commands.md.
  5. If you launch a box for another agent, point it at yolobox and YOLOBOX_CONTEXT_FILE for inside-the-box introspection.
  6. When discussing concurrency, distinguish isolated per-run manifests from shared persistent state: manifests are per-run, but /home/yolo and /var/cache are shared unless --scratch is used.
Files

What ships with it

2 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. 12d ago First seen · 27 lines · 65 tokens per session scan A 8e1ac21eff6a

Subscribe to this mod's changes

yolobox-orchestrator is a skill published in the GitHub repository finbarr/yolobox (641 stars, last pushed 14d ago), licensed MIT. It adds 65 tokens to every session and 494 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens