speckit-companion: Command for Claude Code

.claude/commands/sandbox.md

sandbox is a command for Claude Code from alfredoperez/speckit-companion. It costs 22 tokens per session (841 once invoked), scanned A, original, MIT.

A command for creating or listing small throwaway projects from predefined test recipes. A sandbox is an isolated project used to try or verify something without changing the main repository.

In plain words
What is it for?
Use it to list available recipes and existing sandboxes, or build a sandbox for a test scenario.
Why use it?
It provides known starting states for testing and keeps those temporary projects outside the main codebase.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is alfredoperez/speckit-companion's own configuration. It tells Claude Code how to work on speckit-companion itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything speckit-companion configures →

Reuse

Borrowing it

Nothing to install: this file belongs to alfredoperez/speckit-companion. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/alfredoperez/speckit-companion/main/.claude/commands/sandbox.md
Clone the repo
git clone --depth 1 https://github.com/alfredoperez/speckit-companion

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 sandbox

README.md
[![agentmods](https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/sandbox/github.svg)](https://agentmods.dev/commands/alfredoperez/speckit-companion/sandbox)
Your own site
<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/sandbox"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/sandbox/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 sandbox

Your own site · 80×15
<a href="https://agentmods.dev/commands/alfredoperez/speckit-companion/sandbox"><img src="https://agentmods.dev/badge/commands/alfredoperez/speckit-companion/sandbox.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 841 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.00022 $0.00841
Opus 5.5 $0.00009 $0.00336
Sonnet 5.5 $0.00004 $0.00168
Haiku 4.5 $0.00002 $0.00084

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

Security

Grade A, and why

sandbox 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 19d 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.

.claude/commands/sandbox.md · 55 lines

How it starts

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

Your task

Build one test sandbox, or show what there is. A sandbox is a small throwaway project in a known starting state; the recipes live in the sibling speckit-sandboxes repo and every built sandbox lands under its sandbox root, never in this repo.

Shell state does not persist between Bash calls, so start each one with . .claude/sandboxes-env.sh. It sets $SANDBOXES_REPO (the sibling checkout) and $SANDBOXES_DIR (the sandbox root). If it says there is no checkout, relay that line and stop.

Read $ARGUMENTS

  • empty: list. Print the recipes, then the sandboxes that already exist:

    . .claude/sandboxes-env.sh && "$SANDBOXES_REPO"/new-sandbox.sh --list
    . .claude/sandboxes-env.sh && ls -1 "$SANDBOXES_DIR" 2>/dev/null || echo "(no sandboxes yet)"
    

    Show both as two short lists, with the root's path above the second. Do not build anything. Two folders in the second list are not sandboxes, so say what they are when they show up: bench-cells holds the benchmark's cells and awesome-copilot is /publish-canvas's upstream clone.

  • where: print the sandbox root and nothing else.

    . .claude/sandboxes-env.sh && "$SANDBOXES_REPO"/new-sandbox.sh --where
    
  • <recipe> [name]: build one. The name defaults to the recipe, and a name that is taken is never reused: the new sandbox becomes <name>-2, then -3.

    . .claude/sandboxes-env.sh && "$SANDBOXES_REPO"/new-sandbox.sh <recipe> [name]
    
  • <recipe> [name] --dev: the same, with Companion installed from this checkout in place of the published build. COMPANION_DIR points the recipe here; without it the recipe uses the speckit-companion folder beside the sandboxes repo, which is not this checkout when you are in a worktree.

    . .claude/sandboxes-env.sh && COMPANION_DIR="$PWD" "$SANDBOXES_REPO"/new-sandbox.sh <recipe> [name] -- --dev
    

    A recipe with no Companion (vscode-qa-stock, copilot-stock, claude-mod-stock) refuses --dev; say so and build nothing.

Read the full file on GitHub · 55 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. 19d ago First seen · 55 lines · 22 tokens per session scan A ee227d5a898b

Subscribe to this mod's changes

sandbox is a command published in the GitHub repository alfredoperez/speckit-companion (99 stars, last pushed 6d ago), licensed MIT. It adds 22 tokens to every session and 841 once invoked, about $0.0001 per session on Opus 5.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-10-06.