stay-busy

stay-busy is a skill for Claude Code, Codex from vosslab/vosslab-skills. It costs 50 tokens per session (2,563 once invoked), scanned A, original, MIT.

A skill that keeps an agent manager working when its current task or delegated work is finished or waiting. It finds bounded follow-up tasks that produce useful evidence or completed files.

In plain words
What is it for?
Use it to find next steps, continue investigations, create fallback workstreams, and make progress while delegated agents or the user are unavailable.
Why use it?
It prevents the manager from stopping after the first obvious task when more safe, relevant work can still be done.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present. Also seen: mentions subagents.

Part of the vosslab-skills plugin — 42 skills, 14 agents shipped together

Good fit Use it to find next steps, continue investigations, create fallback workstreams, and make progress while delegated agents or the user are unavailable.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vosslab/vosslab-skills/stay-busy
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 vosslab/vosslab-skills --skill stay-busy
Clone the repo
git clone --depth 1 https://github.com/vosslab/vosslab-skills

Made for: Claude Code, Codex.

Or install vosslab-skills, the plugin that ships this one along with the rest of its 42 skills, 14 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 stay-busy

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/vosslab/vosslab-skills/stay-busy"><img src="https://agentmods.dev/badge/skills/vosslab/vosslab-skills/stay-busy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,563 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.
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.00050 $0.02563
Opus 5 $0.00025 $0.01282
Sonnet 5 $0.00010 $0.00513
Haiku 4.5 $0.00005 $0.00256

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

Security

Grade A, and why

stay-busy 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 11d 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/management/stay-busy/SKILL.md · 282 lines

How it starts

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

Stay busy

Big picture

One-line principle: when stuck, find a solution. When the manager has no obvious next plan task, the answer is more dispatched work, not idle.

Finish the obvious comes first. This skill is layered on top of the "Finish the obvious" core philosophy in docs/REPO_STYLE.md. If a plan task, in-flight workstream, or open verification step still has obvious next actions, the manager takes those FIRST. stay-busy fires only after the obvious queue is empty. See ## Finish before expanding for the gate that enforces this, and Workflow step 2 for where the gate runs.

The failure this skill prevents: the manager spends a few minutes making a plan, then sits idle for hours or days. A short task gets finished and the manager stops, even though the user wanted continued exploration.

This skill exists to inflate scope by roughly two orders of magnitude when the user is away from the keyboard, overnight or across several days. They are going to bed, stepping out, or running a session unattended, and they want to wake up to finished artifacts, not a queue of pending questions to answer.

Success = completed work the user can read on returning. Failure = a stack of "should I do X?" prompts, or a milestone declared done while obvious follow-on testing was skipped.

Four anchor activities, named by the user, define the work stay-busy generates:

  • Write up results. Synthesize completed runs into reports that compare, summarize, or rank. Long-form (25-100 page) reports are a valid single workstream when enough evidence has accumulated to synthesize.
  • A/B (or A/B/C/D) testing. Run methodologies, configurations, or alternative implementations side by side and report the comparison.
  • Side-quest experiments. Launch subagents to explore tangents that may inform future work, labeled SIDE QUEST.
  • Audit the codebase. Read-only correctness, style, contract, and coverage sweeps producing inspectable artifacts.

Default workstream shape in away-mode is expansive, not small. "Small, concrete recovery task" is wrong when the user is asleep. The right shape is a test suite spanning N methodologies, a stress matrix across M configurations, an audit covering K subsystems, a screenshot gallery across V viewports.

Read the full file on GitHub · 282 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. 11d ago First seen · 282 lines · 50 tokens per session scan A aad6905bfd54

Subscribe to this mod's changes

stay-busy is a skill published in the GitHub repository vosslab/vosslab-skills (2 stars, last pushed 15d ago), licensed MIT. It adds 50 tokens to every session and 2,563 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-31.