OpenSandbox is a sandbox platform that gives AI applications APIs, SDKs, and runtimes for creating isolated environments, running commands, and managing files. It is used for coding and GUI agents, browser automation, code execution, agent evaluation, and reinforcement-learning training across Docker and Kubernetes environments. The catalogue entries provide instructions and a skill for working with these sandboxes.
Borrowing it
Nothing to install: this file belongs to opensandbox-group/OpenSandbox. 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/opensandbox-group/OpenSandbox/main/.agents/skills/opensandbox-release-notes/SKILL.mdgit clone --depth 1 https://github.com/opensandbox-group/OpenSandboxWrote 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/skills/opensandbox-group/opensandbox/opensandbox-release-notes)<a href="https://agentmods.dev/skills/opensandbox-group/opensandbox/opensandbox-release-notes"><img src="https://agentmods.dev/badge/skills/opensandbox-group/opensandbox/opensandbox-release-notes/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/skills/opensandbox-group/opensandbox/opensandbox-release-notes"><img src="https://agentmods.dev/badge/skills/opensandbox-group/opensandbox/opensandbox-release-notes.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.00062 | $0.04913 |
| Opus 5.5 | $0.00025 | $0.01965 |
| Sonnet 5.5 | $0.00012 | $0.00983 |
| Haiku 4.5 | $0.00006 | $0.00491 |
Grade A, and why
opensandbox-release-notes 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSandbox Umbrella Release Notes Generator
Generate the hand-authored release notes for a whole-platform (umbrella) OpenSandbox release: docs/releases/X.Y.Z.md, from the template at docs/releases/TEMPLATE.md. The umbrella is the only release train — one version X.Y.Z covers server, all component images, charts, CLI, and every SDK, so the note must classify changes by component, not by repository.
The note is the authoritative copy: the release-umbrella.yml workflow consumes it verbatim for the BOM commit and mirrors it to the GitHub Release. Preflight fails if the file is missing or empty, so the file must exist and be complete before a release is triggered.
Parameters
| Placeholder | Example | Description |
|---|---|---|
<version> |
1.1.0 |
The umbrella version being released (X.Y.Z or X.Y.Z-rc.N) |
<owner>/<repo> |
opensandbox-group/OpenSandbox |
GitHub repository (verify with git remote -v, prefer upstream) |
<baseline> |
release-1.0.0 or per component |
What users upgrade FROM. First look for the previous umbrella release tag release-X.Y.Z; only when none exists (first umbrella release) fall back to each component's last independent legacy release tag. Ask the user only if a baseline cannot be derived |
Baseline derivation
Priority order:
- Previous umbrella tag (the normal case). Find the highest existing
release-X.Y.Ztag below<version>(git tag -l 'release-*'/gh release list). If one exists, that single tag is the baseline for every section — test all PRs against it and move on. - No previous umbrella tag (first umbrella release, e.g.
1.1.0after the legacy era). Fall back to the last independent legacy release tag per component (see the "First Umbrella Version of Every Artifact" table inoseps/0016-*.md, orgh release list):
| Note section | Baseline artifact |
|---|---|
| Server | last server/v* release |
| Execd | last docker/execd/v* release |
| Networking (egress) | last docker/egress/v* release |
| Networking (ingress) | last docker/ingress/v* release |
| Controller (controller, task-executor, CRDs) | last k8s/controller/v* / k8s/task-executor/v* |
| Controller (Helm entries) | last helm/opensandbox/* / helm/opensandbox-controller/* |
| SDKs | last release per language AND per product (python/sandbox/v*, js/code-interpreter/v*, python/mcp/sandbox/v*, …) |
| Misc CLI | last cli/v* release |
| Misc node-agent, docs, CI, deps | no legacy release → include everything in the window |
What ships with it
1 file 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.
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.
- yesterday Changed · +21 lines 5c3c722075da
- 9d ago Changed · +2 lines 8221a180bd09
- 19d ago Changed · -28 lines 63c108192906
- 1mo ago Changed · +12 lines c8b96ad51656
- 1mo ago First seen · 209 lines · 62 tokens per session scan A 89c58ae5418e
opensandbox-release-notes is a skill published in the GitHub repository opensandbox-group/OpenSandbox (16,463 stars, last pushed today), licensed Apache-2.0. It adds 62 tokens to every session and 4,913 once invoked, about $0.0002 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-09-22.
opensandbox-release-notes compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| opensandbox-release-notesopensandbox-group/OpenSandbox | Skill | 16k | today | Apache-2.0 | A | 62 | Claude Code, Codex |
| github-repo-managementmoltis-org/moltis | Skill | 2.9k | 14d ago | MIT | A | 47 | Claude Code, Codex |
| maintainer-opsvllm-project/semantic-router | Skill | 6.4k | yesterday | Apache-2.0 | A | 32 | Claude Code, Codex |
| npmintentic/intentic | Skill | 90 | yesterday | MIT | A | 53 | Claude Code, Codex |
| delivery-operationssabbour/agentweaver | Skill | 7 | yesterday | MIT | A | 19 | Claude Code, Codex |
| docs-release-notessabbour/agentweaver | Skill | 7 | yesterday | MIT | A | 19 | Claude Code, Codex |
| release-notesgetskillseal/skillseal | Skill | 2 | 2mo ago | MIT | A | 28 | Claude Code, Codex |