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.
npx agentmods add skills/computesdk/benchmarks/add-sandbox-providernpx skills add computesdk/benchmarks --skill add-sandbox-providergit clone --depth 1 https://github.com/computesdk/benchmarksWrote 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/computesdk/benchmarks/add-sandbox-provider)<a href="https://agentmods.dev/skills/computesdk/benchmarks/add-sandbox-provider"><img src="https://agentmods.dev/badge/skills/computesdk/benchmarks/add-sandbox-provider.svg" alt="Measured on agentmods" 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.00070 | $0.01121 |
| Opus 5 | $0.00035 | $0.00561 |
| Sonnet 5 | $0.00014 | $0.00224 |
| Haiku 4.5 | $0.00007 | $0.00112 |
Grade A, and why
add-sandbox-provider 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a sandbox provider to the benchmarks
This repo benchmarks ComputeSDK sandbox providers. A provider is wired across four
files. New providers are staged (every change commented out) until the provider's
API secret exists as a GitHub repo secret — then they're activated by uncommenting.
The beam provider is the reference example of a staged provider.
Inputs you need from the user (ask if missing): the provider name (lowercase, as it
appears on npm @computesdk/<name>) and the env var(s) it authenticates with
(e.g. FOO_API_KEY).
1. Verify the package and its factory shape
Never guess the factory name or config keys — confirm against the published package:
npm view @computesdk/<name> version # confirm it exists, get the version
cd /tmp && npm pack @computesdk/<name> # then inspect the type defs:
tar -xzf computesdk-<name>-*.tgz -O package/dist/index.d.ts | grep -nE 'declare const|Config|export'
Note the exported factory (usually <name>) and its config interface — which key holds
the API key, and whether the key falls back to an env var. Most factories take
{ apiKey }; some take { token }, { token, workspace }, etc.
2. Add the dependency
In package.json add "@computesdk/<name>": "^<version>" to
dependencies, in alphabetical order. Then sync the lockfile:
pnpm install
Confirm the diff only added the new package — git diff --stat package-lock.json
(npm may report removing/changing packages while reconciling node_modules on disk;
that's fine as long as the committed lockfile only gained the new entry).
3. Document the env var(s)
In benchmarks/.env.example append a section (staged providers live near the
bottom, by BEAM):
######### <NAME> ########
<NAME>_API_KEY=your_<name>_api_key
4. Stage the provider entry (commented)
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.
- 6d ago First seen · 107 lines · 70 tokens per session scan A b141a0681f4b
add-sandbox-provider is a skill published in the GitHub repository computesdk/benchmarks (113 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 1,121 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.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
konflux-build
Create a manual Konflux build from a PR with configurable image expiry (default 30 days).
devops
DevOps - Docker, CI/CD, cloud infra, monitoring.
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
devops-deployment
Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.