Team Agent Orchestration
affaan-m/ECC
Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates.
Agent skill
by disler in disler/inkwell-agent-sandboxes-and-software-factory
Drive the six-phase sandbox mount system from the host — mount throwaway exe.dev VMs, run the Super Simple Software Factory inside them, watch from outside, harvest the commits, tear down.
$ npx skills add disler/inkwell-agent-sandboxes-and-software-factory --skill sssf-sandbox-orchestrator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install disler/inkwell-agent-sandboxes-and-software-factory sssf-sandbox-orchestrator --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/disler/inkwell-agent-sandboxes-and-software-factory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/sssf-sandbox-orchestrator .claude/skills/sssf-sandbox-orchestrator && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sssf-sandbox-orchestrator" agent skill from https://github.com/disler/inkwell-agent-sandboxes-and-software-factory/tree/main/.claude/skills/sssf-sandbox-orchestrator into .claude/skills/sssf-sandbox-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sssf-sandbox-orchestrator", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/disler/inkwell-agent-sandboxes-and-software-factory/tree/main/.claude/skills/sssf-sandbox-orchestratorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add disler/inkwell-agent-sandboxes-and-software-factory --skill sssf-sandbox-orchestrator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install disler/inkwell-agent-sandboxes-and-software-factory sssf-sandbox-orchestrator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/disler/inkwell-agent-sandboxes-and-software-factory.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/sssf-sandbox-orchestrator .agents/skills/sssf-sandbox-orchestrator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sssf-sandbox-orchestrator" agent skill from https://github.com/disler/inkwell-agent-sandboxes-and-software-factory/tree/main/.claude/skills/sssf-sandbox-orchestrator into .agents/skills/sssf-sandbox-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sssf-sandbox-orchestrator", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add disler/inkwell-agent-sandboxes-and-software-factory --skill sssf-sandbox-orchestrator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install disler/inkwell-agent-sandboxes-and-software-factory sssf-sandbox-orchestrator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/disler/inkwell-agent-sandboxes-and-software-factory.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/sssf-sandbox-orchestrator .cursor/skills/sssf-sandbox-orchestrator && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sssf-sandbox-orchestrator" agent skill from https://github.com/disler/inkwell-agent-sandboxes-and-software-factory/tree/main/.claude/skills/sssf-sandbox-orchestrator into .cursor/skills/sssf-sandbox-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sssf-sandbox-orchestrator", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/disler/inkwell-agent-sandboxes-and-software-factory.git --path .claude/skills/sssf-sandbox-orchestrator--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add disler/inkwell-agent-sandboxes-and-software-factory --skill sssf-sandbox-orchestrator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install disler/inkwell-agent-sandboxes-and-software-factory sssf-sandbox-orchestrator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/disler/inkwell-agent-sandboxes-and-software-factory.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/sssf-sandbox-orchestrator .gemini/skills/sssf-sandbox-orchestrator && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sssf-sandbox-orchestrator" agent skill from https://github.com/disler/inkwell-agent-sandboxes-and-software-factory/tree/main/.claude/skills/sssf-sandbox-orchestrator into .gemini/skills/sssf-sandbox-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sssf-sandbox-orchestrator", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install disler/inkwell-agent-sandboxes-and-software-factory sssf-sandbox-orchestratorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add disler/inkwell-agent-sandboxes-and-software-factory --skill sssf-sandbox-orchestrator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/disler/inkwell-agent-sandboxes-and-software-factory.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/sssf-sandbox-orchestrator .github/skills/sssf-sandbox-orchestrator && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sssf-sandbox-orchestrator" agent skill from https://github.com/disler/inkwell-agent-sandboxes-and-software-factory/tree/main/.claude/skills/sssf-sandbox-orchestrator into .github/skills/sssf-sandbox-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sssf-sandbox-orchestrator", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add disler/inkwell-agent-sandboxes-and-software-factory --skill sssf-sandbox-orchestrator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install disler/inkwell-agent-sandboxes-and-software-factory sssf-sandbox-orchestrator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/disler/inkwell-agent-sandboxes-and-software-factory.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/sssf-sandbox-orchestrator .opencode/skills/sssf-sandbox-orchestrator && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sssf-sandbox-orchestrator" agent skill from https://github.com/disler/inkwell-agent-sandboxes-and-software-factory/tree/main/.claude/skills/sssf-sandbox-orchestrator into .opencode/skills/sssf-sandbox-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sssf-sandbox-orchestrator", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
sssf-sandbox-orchestratorDrive the six-phase sandbox mount system from the host — mount throwaway exe.dev VMs, run the Super Simple Software Factory inside them, watch from outside, harvest the commits, tear down.
Sssf Sandbox Orchestrator is an agent skill from disler/inkwell-agent-sandboxes-and-software-factory. Drive the six-phase sandbox mount system from the host — mount throwaway exe.dev VMs, run the Super Simple Software Factory inside them, watch from outside, harvest the commits, tear down. Use when the user says mount a sandbox, run the factory in a sandbox, spin up N sandboxes, best-of-N, check on a run, harvest a run's commits, or tear down. Keywords - sandbox, mount, exe.dev VM, run id, fan out, best-of-N, harvest, bundle, teardown, reap.
Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 15 other files, including reference files (for example `cookbooks/access_a_running_sandbox.md`, `cookbooks/debug_a_failed_gate.md` and `cookbooks/execute_work.md`).
The repository describes itself as: Inkwell: a small app, the Super Simple Software Factory that builds it, and the rebootable sandbox system that runs both on a throwaway VM. The licence is MIT.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 92f1701. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
justsshgitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use ssh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
OPENROUTER_PROVISIONING_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Sssf Sandbox Orchestrator loads about 2.6k tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 118 tokens; SKILL.md has 1,349 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
.61s, no auth), optional SHA pin, write `.env` with the runtime key |VM's `app/.env`. Never print it, never copy it, never pass it over ssh — `setup`'s gate spends itAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from disler/inkwell-agent-sandboxes-and-software-factory at commit 92f1701, republished under its MIT licence (© disler). 1,349 words, ~2,617 tokens.
.claude/skills/sssf-sandbox-orchestrator/SKILL.md (or your agent's skills folder). This skill also uses 13 other files; get the full folder from GitHub.Drives the out-of-sandbox half of this repo: the sbx namespace under just/sandbox/ that
take a blank exe.dev VM to a health-checked, running factory in ~10s, run work inside it, expose it
to a browser, and — only when a human says so — tear it down.
Every action you take should be a just command a human could type. The recipes hold the
knowledge; this skill holds the judgment about which one to run and how to read the result.
ssh <vm>.exe.xyz '...' or curl to inspect is fine and expected — that is what
just sbx run cmd <id> '<cmd>' exists for, and reading a log or a table needs no ceremony.ssh exe.dev new, a share port, or a detached nohup launch. Those encode measured facts
(mint order, the revocation gate, the proxy retarget, the three detachment pieces) and a
hand-rolled version drops one of them silently.This skill references /sssf and /sandbox-exe-dev rather than duplicating them. /sssf owns
the ADW roster, the handoff contract and the trace-db schema; /sandbox-exe-dev owns the exe.dev
CLI surface. Both move without asking us, and a copy pasted here would be a second source of truth
that goes wrong quietly — a stale model id, a renamed flag. Read them; do not quote them.
Preflight is one command. Run it before the first phase; any failure means report and stop, never work around a missing prerequisite by hand.
just sbx manage doctorIt checks all six in one pass: ssh exe.dev reachable, OPENROUTER_PROVISIONING_KEY set (never
printed), the run-record helper runs, the provisioner is executable,
the models template carries full four-field rate blocks, and the adw layer resolves. Green ends
with sbx doctor: OK.
Two things it does not cover, so check them yourself:
| Check | Command | If it fails |
|---|---|---|
| Factory skill | test -f .claude/skills/sssf/SKILL.md | the ADWs the sandbox runs come from /sssf. Without it there is nothing to mount. |
| VM skill | test -f .claude/skills/sandbox-exe-dev/SKILL.md | read it for exe.dev CLI detail instead of guessing flags. |
Listing a namespace is
just --list sbx, notjust sbx --list. The latter reads--listas a recipe name and errors withJustfile does not contain recipe `sbx --list`. A barejust sbxalso works — it runs the namespace'sdefault, which lists.
| Out-sandbox (you) | In-sandbox (the VM) | |
|---|---|---|
| Lives in | just/sandbox/, sandbox_mount/host/ | just/adws.just (mod adw), adws/, sandbox_mount/guest/ |
| Entry point | just sbx mount, just sbx lifecycle execute, just sbx lifecycle teardown | just adw sdlc "..." |
| Credential | exe.dev account + OpenRouter provisioning key | one disposable runtime key, $50 cap |
The whole repo ships to the sandbox, this skill included. What a sandbox cannot do is USE the
out-sandbox half — just sbx mount there fails on a missing exe.dev account, and create fails on
a missing OPENROUTER_PROVISIONING_KEY. Neither credential ever leaves the host, and that, not file
absence, is what stops a sandbox from mounting sandboxes. Keep the credentials on the host.
Four groups under sbx, plus mount at the top because it is the entry point, not a phase:
just sbx
├── mount the chain: create → fill → setup → observe
├── lifecycle the six phases, for when you need one on its own
├── manage preflight, readback, fleet ops — nothing here is a phase
├── run put work in / look inside: `run cmd`, `run agent`
└── orch boot a host-side orchestrator: `orch cc`, `orch pi`just sbx, just sbx lifecycle, just sbx manage, just sbx run and just sbx orch each list
their own contents when run bare.
| Command | What it does |
|---|---|
just sbx mount RUN_ID [--limit N] | create → fill → setup → observe. Never teardown. Prints the resolved run id and both URLs. |
just sbx lifecycle create RUN_ID [--limit N] | mint sbx-<run-id> ($50 default) + boot the VM, in record → VM → key order |
just sbx lifecycle fill RUN_ID [SHA] | public git clone (2.61s, no auth), optional SHA pin, write .env with the runtime key |
just sbx lifecycle setup RUN_ID | provision.sh + the five-assertion gate |
just sbx lifecycle execute RUN_ID "PROMPT" | full SDLC detached inside the box; returns a pid, records it |
just sbx run cmd RUN_ID '<cmd>' | generic escape hatch, synchronous, runs in app/. Your inspection tool. |
just sbx run agent RUN_ID "PROMPT" | Claude Code inside the box, resumable session — hand off, then keep talking |
just sbx lifecycle observe RUN_ID | start both servers, expose 4501, print URLs. Idempotent. |
just sbx manage list | every run record: state, VM alive, spend |
just sbx manage harvest RUN_ID | pull the run's commits home as a git bundle, fetched into refs/sandbox/<run-id>. Non-destructive, idempotent, run it any time. |
just sbx lifecycle teardown RUN_ID [--no-harvest] | spend → artifacts → harvest → revoke → destroy → close. The only destructive recipe. |
just sbx manage reap [--yes] | delete orphaned sbx-* keys. Dry run by default. Run it at the start of a session. |
The run id is the handle for every phase. create appends -<date>-<6 hex> if you did not, and
prints what it settled on — use that string, not the one you typed.
The five gate assertions (setup): A git integrity (status --porcelain clean, HEAD
matches the recorded sha) · B pi --list-models non-empty — it exits 0
while empty · C every roster model answers a ping · D pi reports non-zero cost, which
proves the rate table loaded · E remaining credit. A failure reports, stops, and leaves the VM
alive.
| Activity | When to read | File |
|---|---|---|
| Understand the recipes before running any | first time, or when a recipe surprises you | cookbooks/just_command_model.md |
| Stand up one sandbox end to end | "mount a sandbox", "run this in a sandbox" | cookbooks/mount_one.md |
| Put work into a mounted box | "build X in there", "ask the agent", picking run cmd vs lifecycle execute vs run agent | cookbooks/execute_work.md |
| Watch a run and report it back | "check on the run", "is it done", "show me the URLs" | cookbooks/observe_and_report.md |
| Give the user access to a running box | "get me into the sandbox", a shell in there, talk to the in-box agent | cookbooks/access_a_running_sandbox.md |
| A gate assertion failed | setup exited non-zero, or the box looks wrong | cookbooks/debug_a_failed_gate.md |
| Spin up N and pick a winner | "best-of-N", "three variants", "diff the runs" | cookbooks/fan_out_n.md |
| Shut a run down, clean up keys | the human decided to tear down; orphaned sbx- keys | cookbooks/teardown_and_reap.md |
| Reference | Covers |
|---|---|
| references/phases.md | what each of the six phases does, in order, and why the order is that order |
| references/kickoff_paths.md | the two ways work enters a box: direct (lifecycle execute, a command) vs agent-mediated (run agent, a delegation) |
| references/run_record.md | .sandbox/runs/<id>.json — the closed schema, who writes each field, who reads it |
| references/models.md | the roster, per-million rates, the mandatory four-field cost block, ZDR |
| references/gotchas.md | every trap that cost a debugging cycle, with the symptom it produces |
mount stops at observe on purpose and nothing chains into teardown. A VM left
running is a bill; a VM destroyed early is the evidence and the artifacts, gone. harvest is
the exception you may run freely — it only reads the box and only writes refs/sandbox/, so
run it as soon as a run commits rather than letting the commits wait on a teardown decision.just adw sdlc "..." here runs the factory on the engineer's
laptop — the exact collision this system exists to remove. Work goes in through
just sbx lifecycle execute / just sbx run agent, always.just sbx run cmd <id> '...' your way to the cause, fix it, re-run
just sbx lifecycle setup. Re-running setup is safe..sandbox/runs/<id>.key (0600) and inside the
VM's app/.env. Never print it, never copy it, never pass it over ssh — setup's gate spends it
from inside the box for exactly that reason. The provisioning key never leaves the host.create. The sbx- prefix is the entire safety model for reap; the
engineer's personal keys carry no prefix and deleting one is unrecoverable.teardown have.© disler, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 13 other files (references) in .claude/skills/sssf-sandbox-orchestrator of disler/inkwell-agent-sandboxes-and-software-factory.
Open the folder on GitHubat commit 92f1701
Sssf Sandbox Orchestrator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sssf Sandbox Orchestrator this skilldisler/inkwell-agent-sandboxes-and-software-factory | 161 | — | ~2.6k | Automated safety check: Notes | MIT | |
| Team Agent Orchestrationaffaan-m/ECC | 277k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Orca Orchestrationstablyai/orca | 89k | — | ~916 | Automated safety check: Pass | MIT | |
| Agent Orchestrator Taskruvnet/ruflo | 74k | 2 repos | ~1k | Automated safety check: Pass | MIT | |
| Orchestratesickn33/agentic-awesome-skills | 47k | 1 repos | ~692 | Automated safety check: Pass | MIT | |
| Agent Sandboxruvnet/ruflo | 74k | 2 repos | ~777 | Automated safety check: Pass | MIT |
affaan-m/ECC
Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates.
stablyai/orca
Coordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator…
ruvnet/ruflo
Agent skill for orchestrator-task - invoke with $agent-orchestrator-task
sickn33/agentic-awesome-skills
Coordinate focused subagents on substantial work, keep their ownership non-overlapping, and integrate verified results.
ruvnet/ruflo
Agent skill for sandbox - invoke with $agent-sandbox. An agent skill from ruvnet/ruflo.
vercel/next.js
Benchmark React or Next.js changes on Vercel Sandbox VMs with paired A/B statistics: react PR/commit vs base, or Next.js PR/commit vs base, measured end-to-end through the bench/render-pipeline app…
disler/inkwell-agent-sandboxes-and-software-factory
Drive herdr — the terminal-native agent multiplexer (herdr.dev) — from natural language.
disler/inkwell-agent-sandboxes-and-software-factory
Operate exe.dev persistent VMs via SSH/HTTPS for safe code execution and file operations.
Drive the six-phase sandbox mount system from the host — mount throwaway exe.dev VMs, run the Super Simple Software Factory inside them, watch from outside, harvest the commits, tear down. Sssf Sandbox Orchestrator is an agent skill from disler/inkwell-agent-sandboxes-and-software-factory.dev VMs, run the Super Simple Software Factory inside them, watch from outside, harvest the commits, tear down.
Sssf Sandbox Orchestrator fits situations like: the user says mount a sandbox; run the factory in a sandbox; spin up N sandboxes; harvest a runs commits.
Run `npx skills add disler/inkwell-agent-sandboxes-and-software-factory --skill sssf-sandbox-orchestrator -a claude-code`. Or copy the skill folder (.claude/skills/sssf-sandbox-orchestrator in disler/inkwell-agent-sandboxes-and-software-factory) into .claude/skills/sssf-sandbox-orchestrator in your project. Claude Code loads it when a task matches its description.
Run `npx skills add disler/inkwell-agent-sandboxes-and-software-factory --skill sssf-sandbox-orchestrator -a codex`. Or copy the skill folder (.claude/skills/sssf-sandbox-orchestrator in disler/inkwell-agent-sandboxes-and-software-factory) into .agents/skills/sssf-sandbox-orchestrator in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add disler/inkwell-agent-sandboxes-and-software-factory --skill sssf-sandbox-orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sssf-sandbox-orchestrator, .gemini/skills/sssf-sandbox-orchestrator, .github/skills/sssf-sandbox-orchestrator and .opencode/skills/sssf-sandbox-orchestrator in your project.
Going by SKILL.md and its folder, Sssf Sandbox Orchestrator needs the command-line tools its instructions call (just, ssh and git) and credentials named OPENROUTER_PROVISIONING_KEY. Our summary lists: A credential in OPENROUTER_PROVISIONING_KEY.
SKILL.md contains no URLs. Its commands use ssh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Sssf Sandbox Orchestrator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 13k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Sssf Sandbox Orchestrator: Team Agent Orchestration (affaan-m/ECC, 277k stars), Orca Orchestration (stablyai/orca, 89k stars), Agent Orchestrator Task (ruvnet/ruflo, 74k stars) and Orchestrate (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
disler (a GitHub user) maintains it in disler/inkwell-agent-sandboxes-and-software-factory, which has 161 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on August 9, 2026.
Source: disler/inkwell-agent-sandboxes-and-software-factory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.