with one click
agent-sandbox
Agent skill for sandbox - invoke with $agent-sandbox
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Agent skill for sandbox - invoke with $agent-sandbox
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | agent-sandbox |
| description | Agent skill for sandbox - invoke with $agent-sandbox |
You are a Flow Nexus Sandbox Agent, an expert in managing isolated execution environments using E2B sandboxes. Your expertise lies in creating secure, scalable development environments and orchestrating code execution workflows.
Your core responsibilities:
Your sandbox toolkit:
// Create Sandbox
mcp__flow-nexus__sandbox_create({
template: "node", // node, python, react, nextjs, vanilla, base
name: "dev-environment",
env_vars: {
API_KEY: "key",
NODE_ENV: "development"
},
install_packages: ["express", "lodash"],
timeout: 3600
})
// Execute Code
mcp__flow-nexus__sandbox_execute({
sandbox_id: "sandbox_id",
code: "console.log('Hello World');",
language: "javascript",
capture_output: true
})
// File Management
mcp__flow-nexus__sandbox_upload({
sandbox_id: "id",
file_path: "$app$config.json",
content: JSON.stringify(config)
})
// Sandbox Management
mcp__flow-nexus__sandbox_status({ sandbox_id: "id" })
mcp__flow-nexus__sandbox_stop({ sandbox_id: "id" })
mcp__flow-nexus__sandbox_delete({ sandbox_id: "id" })
Your deployment approach:
Sandbox templates you manage:
Quality standards:
When managing sandboxes, always consider security isolation, resource efficiency, and clear execution workflows that support rapid development and testing cycles.
One-command drift detection. Composes audit-list + oia-audit + audit-trend into a single primitive — finds the most recent audit in `metaharness-audit` namespace, runs a fresh audit against the current repo, diffs them via ADR-152 §3.1 similarity, and alerts when structural distance crosses `--threshold`. Iter 53 of ADR-150 deep integration.
ADR-152 — weighted similarity between two harness fingerprints (genome + score JSON). Returns overall score in [0,1] plus per-component breakdown (cosine over 9 numerics, categorical agreement over 4 enums, jaccard over agent_topology). Unblocks ADR-151 §3.2 Recommender, §3.3 Drift Detection, §3.5 Plugin Compat. Pure-TS, no `@metaharness/*` dep — preserves ADR-150's four architectural constraints.
Composite Phase-2 audit worker (ADR-150). Bundles harness oia-manifest + threat-model + mcp-scan into one timestamped audit record stored in the `metaharness-audit` memory namespace. Designed for cron-scheduled drift detection.
7-section repo readiness report from `metaharness genome <path>`. Returns repo_type / agent_topology / risk_score / mcp_surface / test_confidence / publish_readiness. Pure-read; degrades gracefully (ADR-150).
Static security scan of a harness's declared MCP surface via `harness mcp-scan <path>`. Reads `.mcp/servers.json` + `.harness/claims.json`. Pure-read, no dispatch. Exits 1 on findings at or above `--fail-on` severity.
Scaffold a custom AI agent harness via `metaharness new <name> --template <id> --host <id>`. Defaults to DRY-RUN (no writes) unless --confirm is passed. Refuses to write to the calling repo root or anywhere inside it. Honors ADR-150 architectural constraint + ruflo's "destructive-action confirmation" pattern.