sandbox-agent is an HTTP and server-sent-events service that runs coding agents inside isolated sandboxes and lets another application control them remotely. Developers use it to run agents such as Claude Code, Codex, OpenCode, Cursor, Amp, or Pi while streaming events, managing sessions, and storing transcripts. The catalogue entries provide agents, skills, commands, instructions, and MCP integration for working with the service.
Borrowing it
Nothing to install: this file belongs to rivet-dev/sandbox-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rivet-dev/sandbox-agent/main/.claude/commands/post-release-testing.mdgit clone --depth 1 https://github.com/rivet-dev/sandbox-agentWrote 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.
[](https://agentmods.dev/commands/rivet-dev/sandbox-agent/post-release-testing)<a href="https://agentmods.dev/commands/rivet-dev/sandbox-agent/post-release-testing"><img src="https://agentmods.dev/badge/commands/rivet-dev/sandbox-agent/post-release-testing/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.
<a href="https://agentmods.dev/commands/rivet-dev/sandbox-agent/post-release-testing"><img src="https://agentmods.dev/badge/commands/rivet-dev/sandbox-agent/post-release-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00339 |
| Opus 5.5 | $0.00000 | $0.00136 |
| Sonnet 5.5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade C, and why
post-release-testing scanned grade C with 2 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 1mo 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://releases.rivet.dev/sandbox-agent/0.4.x/install.sh | sh && Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Installs sandbox-agent via curl from releases.rivet.dev What it actually says
Post-Release Testing Agent
You are a post-release testing agent. Your job is to verify that a sandbox-agent release works correctly.
Environment Setup
First, source the environment file:
source ~/misc/env.txt
Tests to Run
Run these tests in order, reporting results as you go:
1. Docker Example Test
RUN_DOCKER_EXAMPLES=1 pnpm --filter @sandbox-agent/example-docker test
This test:
- Creates an Alpine container
- Installs sandbox-agent via curl from releases.rivet.dev
- Verifies the
/v1/healthendpoint responds correctly
2. E2B Example Test
pnpm --filter @sandbox-agent/example-e2b test
This test:
- Creates an E2B sandbox with internet access
- Installs sandbox-agent via curl
- Verifies the
/v1/healthendpoint responds correctly
3. Install Script Test
Manually verify the install script works in a fresh environment:
docker run --rm alpine:latest sh -c "
apk add --no-cache curl ca-certificates libstdc++ libgcc bash &&
curl -fsSL https://releases.rivet.dev/sandbox-agent/0.4.x/install.sh | sh &&
sandbox-agent --version
"
Instructions
- Run each test sequentially
- Report the outcome of each test (pass/fail)
- If a test fails, capture and report the error output
- Provide a summary at the end with overall pass/fail status
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.
- 1mo ago First seen · 57 lines · 0 tokens per session scan C 301435d9f6ea
post-release-testing is a command published in the GitHub repository rivet-dev/sandbox-agent (1,609 stars, last pushed 13d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 339 tokens. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
vios-sqa
VIOS SQA agent — build containers, deploy, run BDD tests, and validate web UI.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
qa-pr
Device-test a GitHub pull request on iOS simulator, Android emulator, and/or physical device. Installs the PR head via rn-dev-agent and reports pass/fail with repro steps and screenshots.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
test
Generate integration tests for Alfresco extensions using Testcontainers (self-contained, no pre-running ACS required).
run-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.