Guía a los usuarios en la instalación inicial de capas de agentes seguras, incluyendo sandboxing, sistemas de aprobación y entornos limpios.
- Estrellas en GitHub
- 145
- Archivos
- 7
- Último commit
- 12 nov 2026
- Licencia
- Apache-2.0
- Herramientas permitidas
- —
¿Qué hace la skill isolated-setup-install?
Guía a los usuarios en la instalación inicial de capas de agentes seguras, incluyendo sandboxing, sistemas de aprobación y entornos limpios.
Resumen generado a partir del SKILL.md de la skill.
Sobre la skill isolated-setup-install
Configurar capas de agentes seguras, como sandboxing y sistemas de aprobación, es lo que este SKILL facilita para desarrolladores que utilizan Claude Code, Codex, Antigravity, Pi o Goose. Actúa como una rampa de acceso interactiva para instalaciones por primera vez o para usuarios que trabajan en clones nuevos y máquinas nuevas que carecen de una configuración previa. El SKILL guía a los usuarios a través de un proceso paso a paso para establecer entornos limpios y configuraciones seguras sin ejecutar nunca sudo ni modificar automáticamente los archivos rc de la shell.
Un agente debería cargar este SKILL cuando un usuario solicite una configuración segura en una sesión nueva. Se apoya en archivos de configuración locales, ajustes específicos del proyecto y scripts proporcionados por el framework para garantizar que el entorno cumpla con los requisitos de seguridad. El proceso incluye la verificación de la versión del agente frente a un mínimo requerido y la gestión de listas de permitidos (allowlists) para el sandbox. Para mantener la seguridad, el SKILL proporciona los comandos exactos para que el usuario los copie y pegue en su terminal en lugar de ejecutar comandos con elevación de privilegios por sí mismo.
Lo que un agente puede hacer con ella
- 1Instalación segura de agentes por primera vezGuía a un usuario a través de la configuración inicial de las capas de sandboxing y aprobación para un nuevo entorno de agente.
- 2Configurar el acceso al sistema de archivos del sandboxAñade la raíz del proyecto como una ruta absoluta a los ajustes locales para asegurar que el sandbox pueda leer los archivos del proyecto.
- 3Verificar una configuración segura existenteComprueba si la instalación actual es correcta y está actualizada con el pin del proyecto.
- 4Gestionar la deriva de configuración (configuration drift)Detecta discrepancias entre los bloqueos de la máquina local y los pins del proyecto commiteados para proponer las actualizaciones necesarias.
Escrito a partir del SKILL.md de la skill. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar la skill isolated-setup-install
Cada comando copia la carpeta de la skill al directorio de skills del cliente. Reinicia el cliente o inicia una nueva sesión para cargarla.Instalar la skill isolated-setup-install en Plugin
/plugin marketplace add apache/magpie /plugin install magpie-setup@apache-magpie
Instalar la skill isolated-setup-install en Claude Code
~/.claude/skills/isolated-setup-install/SKILL.md
$ npx degit apache/magpie/plugins/magpie-setup/skills/isolated-setup-install ~/.claude/skills/isolated-setup-installInstalar la skill isolated-setup-install en Claude Code (project)
.claude/skills/isolated-setup-install/SKILL.md
$ npx degit apache/magpie/plugins/magpie-setup/skills/isolated-setup-install .claude/skills/isolated-setup-installInstalar la skill isolated-setup-install en Codex
~/.agents/skills/isolated-setup-install/SKILL.md
$ npx degit apache/magpie/plugins/magpie-setup/skills/isolated-setup-install ~/.agents/skills/isolated-setup-installInstalar la skill isolated-setup-install en Gemini CLI
~/.gemini/skills/isolated-setup-install/SKILL.md
$ npx degit apache/magpie/plugins/magpie-setup/skills/isolated-setup-install ~/.gemini/skills/isolated-setup-installInstalar la skill isolated-setup-install en Claude.ai
npx degit apache/magpie/plugins/magpie-setup/skills/isolated-setup-install isolated-setup-install && zip -r isolated-setup-install.zip isolated-setup-install # claude.ai → Customize → Skills → + → Create skill → Upload a skill → isolated-setup-install.zip
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Superó nuestras comprobaciones automáticas. No es una auditoría de seguridad: lee los scripts antes de dejar que un agente los ejecute. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesibleapache/magpie/plugins/magpie-setup/skills/isolated-setup-install is public and reachablegithub.com/apache/magpie/tree/HEAD/plugins/magpie-setup/skil ↗Aprobado
- Licencia de código abierto (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit 2026-11-12github.com/apache/magpie/commits ↗Aprobado
- Sin descargar y ejecutar ni robo de credenciales en los scripts1 script read; no download-and-run, remote eval, base64 execution or credential uploadAprobado
- Sin instrucciones ocultas en SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/apache/magpie/blob/HEAD/plugins/magpie-setup/skil ↗Aprobado
- Las herramientas preaprobadas están acotadasNo pre-approved tools; the agent asks before using onegithub.com/apache/magpie/blob/HEAD/plugins/magpie-setup/skil ↗Aprobado
- SKILL.md sigue el formato de Agent Skillsthe description does not say when to use the skillgithub.com/apache/magpie/blob/HEAD/plugins/magpie-setup/skil ↗Hallazgo
SKILL.md
Ver en GitHubsetup-isolated-setup-install
Runtime routing (run before the Claude-specific procedure)
Use the operator's explicitly requested runtime when supplied; otherwise use the active session's runtime. An installed executable or configuration directory alone does not select a runtime. For the routing below, treat that selection as the active harness.
Determine the active harness from the session metadata and executable.
When it is Codex, Antigravity, Pi, Goose or Copilot CLI, follow that harness's paragraph in runtime-routing.md.
When the harness is Claude Code, continue below. If the harness cannot be determined from the session or executable, stop and report that; never guess and never prompt.
This skill is the on-ramp for adopters who do not yet have the
secure setup running. It is a thin walkthrough wrapper around the
canonical install path documented in
docs/setup/secure-agent-setup.md. The
authoritative content lives there; this skill exists so an adopter
can say "set up the secure agent setup" in a fresh session and
land in the right step-by-step flow without first reading the
document.
Adopter overrides
Before running its default behaviour, this skill consults
setup-isolated-setup-install.md in the personal layer
(.apache-magpie-local/ when the project adopted Magpie, falling back to the main checkout's in a linked worktree,
or <git-common-dir>/apache-magpie/ when Magpie is only installed; applied first, wins on conflict) and
.apache-magpie-overrides/setup-isolated-setup-install.md (committed, project-wide)
in the adopter repo, if present, and applies any agent-readable overrides it finds.
See docs/setup/agentic-overrides.md for the contract.
Hard rule: agents NEVER modify the snapshot under <adopter-repo>/.apache-magpie/.
Local modifications go in the override file; framework changes go via PR to apache/magpie.
Snapshot drift
Also at the top of every run, this skill compares the
gitignored .apache-magpie.local.lock (per-machine
fetch) against the committed .apache-magpie.lock
(the project pin). On mismatch the skill surfaces the
gap and proposes
setup update.
The proposal is non-blocking — the user may defer if
they want to run with the local snapshot for now. See
docs/setup/install-recipes.md § Subsequent runs and drift detection
for the full flow.
Drift severity:
- method or URL differ → ✗ full re-install needed.
- ref differs (project bumped tag, or
git-branchlocal is behind upstream tip) → ⚠ sync needed. svn-zipSHA-512 mismatches the committed anchor → ✗ security-flagged; investigate before upgrading.
Golden rules
- Do not auto-run privilege-elevating commands. Anything that
needs
sudo(apt / dnf installs, system-wide writes) is printed for the user to copy-paste into their own terminal. The skill never invokessudoitself. - Do not edit shell rc files without approval.
~/.bashrc/~/.zshrcmodifications (sourcingagent-iso.sh, the optionalalias claude='claude-iso') are surfaced as the exact line to add; the user pastes it themselves. The skill confirms the rc file path with the user first; it does not assume. - Do not overwrite an existing settings file silently. If the
user already has a project
.claude/settings.jsonor a user-scope~/.claude/settings.json, the skill diffs the desired merge against the existing file and asks for explicit approval before writing. The merge carries the framework'spermissions.allowset (the read-only reads:ghreads, the vetted-ops read dispatcher, archive / mailbox / roster MCP reads, registryWebFetchhosts) alongsidedenyandask— leaving it out makes every skill read prompt. Only read-only entries belong inallow. Re-installs / partial-state recoveries are common — the skill must not blow away an unrelated pre-existing hook orpermissions.askrule. The desired merge includes the agent-guardhooks.PreToolUseentry (matcherBash, command running the user-scope~/.claude/scripts/agent-guard.py) — the deterministic guard fromtools/agent-guard. Install the script as~/.claude/scripts/agent-guard.pyand populate~/.claude/scripts/guards.d/from both the engine's bundledguards.d/*.pyand every skill-ownedskills/*/guards/*.py(so skill-owned guards likemention/mark-readyare active), alongside the other user-scope scripts (Step P); wire thePreToolUseentry once, and preserve any pre-existinghooksentries. - Stop on the first failure. If a step fails (manifest read fails, framework path wrong, an existing file conflicts in a way the user has not yet decided about), stop and report. Do not push past a failure to the next step.
Up-front confirmations
Before walking any install step, confirm with the user:
- OS / distro. macOS, Ubuntu / Debian (apt), Fedora / RHEL (dnf), or Arch / NixOS / other. macOS skips bubblewrap + socat (Seatbelt is built-in); Linux installs both per the distro shortcut.
- Framework checkout path. The path to the user's local
magpieclone. Required to readtools/agent-isolation/pinned-versions.toml,.claude/settings.json, and thetools/agent-isolation/*.shscripts. If the user does not have a clone, walk them throughgit clonefirst. - Fresh install or re-install. For a re-install on a partial
existing state, the skill must enumerate the existing wiring
(project settings.json, user settings.json, hooks dir, the
agent-guard
hooks.PreToolUseentry +~/.claude/scripts/agent-guard.py, shell rc) before any merge so the user knows what is being preserved vs replaced. - Sync repo (optional). Whether the user maintains a
private dotfile-style
~/.claude-configrepo per Syncing user-scope config across machines. If yes, the skill installs user-scope scripts as symlinks into~/.claude-config/scripts/rather thancp-ing into~/.claude/scripts/— the symlink approach is what makes sync push the upgrades to other machines automatically. Exceptcontainer-gateway-hook.sh, which is always a plain copy owned by the user: the managed-settings dispatcher that runs it refuses a symlink, whose target could be swapped after the checks. A symlink already in its place is replaced by a copy (rmthe link first — acponto it would write through it into the sync repo), andsetup-isolated-setup-updatereports the copy when it drifts from the framework's.
Walk-through
Follow the canonical step list at docs/setup/secure-agent-setup.md → Adopter setup → Via a Claude Code prompt. Each step in that list maps 1:1 to a step in this skill. Do not re-write the list here — read the doc, follow it, and surface each sub-step with the user. The doc names are the source of truth; the skill is the runner.
For the verification step at the end, hand off to the
setup-isolated-setup-verify skill rather than re-walking the checklist
inline.
Agent harness — install @latest, enforce the floor
claude-code is not pinned to an exact version. Install it with
npm install -g --no-save @anthropic-ai/claude-code@latest (the
command in the doc's install list) — latest always carries the newest
permission-rule / sandbox / prompt-injection fixes. The manifest's
[tools.claude-code] table in
pinned-versions.toml
declares a min_version floor, not a pin. Because this install is
driven from Claude Code, apply the same hard gate
setup-isolated-setup-verify check 5 applies: read the running
version (command claude --version, which skips an
alias claude=claude-iso) and, if it is below min_version,
hard-fail — stop the install, tell the operator to upgrade to
@latest, and have them re-run. The secure setup must not be stood up
on a below-floor runtime.
Step P — Project-root coverage in the sandbox allowlists
The harness drops the literal . when it pre-resolves
sandbox.filesystem.allowRead: ["."], so a session in a fresh clone can
write to the project root but not read from it. The fix is to add the root
as an absolute path to the project-local settings.local.json.
This step asks one question first — per-project or whole-user scope — and the whole-user answer overrides git's hook lookup for every repository on the machine, so it carries a disclosure the operator has to acknowledge.
Full procedure, both scopes and both whole-user flavours:
step-p-sandbox-allowlists.md.
Step V — The vetted-ops split and exclusion
Only applies when the adopter routes forge operations through the
vetted-ops dispatcher — i.e. the repo has
.apache-magpie-overrides/tools/vetted-ops/config.toml, the maintainer
keeps a personal one (<personal layer>/tools/vetted-ops/config.toml,
for a project that has not adopted Magpie), or the operator asks for the
dispatcher to be wired now. If neither is
true, skip this step, report it as n/a, and continue with the
next step: a missing policy is never a blocker for this install.
Do not create a policy the project has not asked for.
Only with the sandbox on. The allow rules and sandbox exclusions
below are a permission bypass: they let the dispatcher run without a
prompt, and outside the sandbox. They are safe only because the sandbox
confines everything else. If the sandbox is not enabled for this
session (Step P declined, or sandbox.enabled is not true in the
scope being wired), skip this step, say so, and leave every vetted
operation behind its normal prompt.
Full procedure, including Step V.1 (read-only vetted ops never prompt):
step-v-vetted-ops.md.
Step R — The adversarial-review exclusion
Only applies when the magpie-adversarial-review plugin is installed. If it
is not, skip this step and say so.
Full procedure: step-r-adversarial-review.md.
Step W — Working directories for the read block
Where the vetted-ops dispatcher is used, Step V.1 already requires
permissions.blockReadsOutsideWorkingDirectories to be off, and these
entries cannot stand in for that: they do not stop the vetted-op-read
prompt. They remain useful for the agent's own reads of the scratch root
where the block is on for other reasons.
Nothing extra to write: the sandbox-add-project-root.sh run in Step P also
adds /tmp/claude-<uid>, resolved, to permissions.additionalDirectories of
each worktree's project-local settings.local.json. Under
permissions.blockReadsOutsideWorkingDirectories the skills read it on every
run; without the entry each read prompts, and a bulk sync multiplies that by
its gatherer agents. The script also removes $HOME/.claude/magpie where an
earlier version added it.
After Step P, show the operator the resulting additionalDirectories list and
check three things:
-
Never
~/.claude/magpie. If any scope lists$HOME/.claude/magpieor a parent of it, propose removing it. A working directory is writable to sandboxed Bash, and the vetted-ops commands run from that checkout outside the sandbox./add-dirhas the same effect for a session. -
No glob and no
~. If the operator already has an entry such as/tmp/claude-*in any scope, say it does nothing: the setting matches literal paths only, so the glob is listed but never matched. -
Nothing per-host in a synced or committed file. If the operator put the paths in a user-scope
~/.claude/settings.jsonthat is synced across machines, or in the committed project settings, suggest moving them: they name this host's uid.
Rationale and the rules in full:
docs/setup/secure-agent-setup.md → Working directories under the read-outside-working-directories block.
Step U — Host-only uv state
The excluded uvx / uv run commands, MCP servers launched with uv, hooks
that call python3 and the operator's own terminal all run uv-managed code
outside the sandbox. None of it may come from a directory a sandboxed command
can write:
-
~/.local/share/uvis read-only to the sandbox. No scope may list it, or a parent of it, inallowWriteoradditionalDirectories. The Step P helper removes the write an earlier version added; propose removing any other by hand. -
The host gets its own uv cache. Read
~/.config/uv/uv.toml. Unless it sets acache-dirthat is absolute and, symlinks resolved, outside every directory a sandboxed command can write (everyallowWriteandadditionalDirectoriesentry in any scope, every project root, and the roots the sandbox writes without a grant (/tmp,/private/tmp,/var/folders,/private/var/folders,$TMPDIR)), stage it withcache-dir = "<resolved $HOME>/.local/share/uv-host/cache"added, keeping every other setting, and give the operator the copy command:Edit(~/.config/uv/**)keeps the agent from writing it. Never~(uv does not expand it there) and never a relative path. -
The sandbox cannot read that file.
permissions.denycarriesRead(~/.config/uv/uv.toml)andEdit(~/.config/uv/**)(both in the framework's.claude/settings.json, so Step 2's copy brings them). Sandboxed uv then keeps its default, writable cache. -
Sandboxed prek gets its own home. The
enventry is needed only where a repository uses prek (aprek.toml,.pre-commit-config.yamlor.pre-commit-config.yml, or a hook that runs it: detection); the deny is always kept, since the default home is per-user. The settings carry"env": {"PREK_HOME": "~/.cache/prek-sandbox"}andpermissions.denycarriesEdit(~/.cache/prek/**)(both in the framework's.claude/settings.json): a terminal's git hooks run prek outside the sandbox from~/.cache/prek. The whole-user dispatcher (Step P) gives hooks that Claude Code runs outside the sandbox a host-only home and cache root too; if a repository sets its owncore.hooksPath, propose unsetting it so the dispatcher runs there.
Then hand the operator the reinstall commands from the doc to run in a
terminal: interpreters and tools the sandbox could write before may already
have been changed. Rationale and commands:
docs/setup/secure-agent-setup.md → Host-only uv state.
Step T — Local agent settings
The committed .claude/settings.json is only the shared floor; the rest
of a working setup is personal and goes in .claude/settings.local.json.
Build and hand over that file exactly as
setup update → Reconcile the local agent settings
does: the MCP tools for families installed here but not adopted by the
project and, only when this project is the Magpie framework checkout,
its template (tools/agent-isolation/claude-settings.local.template.json).
Never stage that template into another project: it would widen that
project's sandbox beyond what its maintainers configured. An agent
cannot write that file, so stage it and give the user the copy command.
ASF network fragment selection: Follow
setup update → ASF network fragment selection
when building the proposed local settings. Select the reviewed ASF
fragment only for an explicitly declared ASF project. Preserve the
existing staged-copy and user-approval process. Never install ASF
network grants in user-scope settings or the shared gateway baseline.
Steps K, L, M and B — optional extras
None of these is needed for a working install. Walk the one the operator
asks for: a hardware security key (K), the container gateway (L), the
eval-harness exclusion (M), or the exclusion for the third-party
roborev CLI (B) — offer B
unprompted when command -v roborev finds it.
Procedures: optional-steps.md.
After the install lands
Tell the operator what to look for in the footer, and what each state means. This is the one piece of the install they will see on every render afterwards, so a wrong reading here persists:
| Tag | Means |
|---|---|
[sandbox] green |
sandboxed, and still prompting per command |
[sandbox-auto] yellow |
sandboxed, not prompting per command — auto-allow; wider blast radius, which is why it is not green |
[NO SANDBOX] bold red |
not sandboxed; the state this install exists to make impossible to miss |
Captures of each are in What a session looks like; point the operator there rather than describing the colours twice.
Two things to say explicitly, because both are counter-intuitive:
- The tag reads the settings files, not the running process. A CLI flag that disables sandboxing mid-session is not visible here. Pair it with the bypass-warn hook, which fires per call.
- Yellow is not a warning that something is broken. Auto-allow is a deliberate, common choice; the colour distinguishes two postures rather than flagging a fault.
Suggest two follow-up routines the user can wire later:
setup-isolated-setup-verify— re-run after every Claude Code upgrade or settings-file edit, to confirm denials still fire as expected. The "did a denial silently turn into an allow?" signal is exactly what this skill exists for.setup-isolated-setup-update— periodic check for framework updates, pinned-tool upgrade candidates, and drift between the installed user-scope copies and the framework's source-of-truth. The pre-flight of every skill proposes it for them once the install is recorded (below): after an upgrade that changes the secure-setup files, and weekly otherwise.
Record the install so that pre-flight knows the isolated setup is used on this machine and what it was installed against:
PYTHONPATH="$HOME/.cache/apache-magpie/preflight" \
python3 -P -m setup_preflight.isolated record-update
It writes the isolated_setup block of the personal layer's
reconciled.json (<git-common-dir>/apache-magpie/ when the project has
not adopted Magpie, .apache-magpie-local/ when it has) and nothing
else. Skip it when the command cannot find setup_preflight — say that
/magpie-setup:setup config installs the checker, and that the reminders start
once it is there.
Check that the vetted-ops plugin is installed. magpie-vetted-ops
is part of the baseline: the family skills run their forge operations
through its dispatcher, and Step V's permission rules point at it.
If the harness's plugin listing lacks it, propose
claude plugin install magpie-vetted-ops@apache-magpie
(codex plugin add magpie-vetted-ops@apache-magpie on Codex) and run it once the operator confirms.
Where the harness has no plugin CLI, print the command instead of running it.
Always propose shared-config sync once the install lands.
Regardless of whether the operator already maintains the
~/.claude-config sync repo, proactively offer to run
setup-shared-config-sync as a follow-up:
- If the
~/.claude-configsync repo is already in place, the skill commits + pushes the local modifications (the user-scope scripts, hooks, and settings this install just wired up) so the other machines pick them up. - If the operator does not yet have
~/.claude-config, thesetup-shared-config-syncskill bootstraps it (clones the default private remote if it exists, or creates a fresh private remote and scaffolds the layout). Mention this so a first-time operator knows the follow-up will set sync up from scratch — the point of proposing it is precisely so the just-installed config does not stay machine-local.
Surface it as an offer for the operator to accept, not an auto-run — the sync skill has its own confirmation gates before it commits or pushes anything.
Archivos de esta skill
7Preguntas sobre la skill isolated-setup-install
¿Cómo instalo la skill isolated-setup-install en Claude Code?
Ejecuta npx degit apache/magpie/plugins/magpie-setup/skills/isolated-setup-install ~/.claude/skills/isolated-setup-install. Claude Code carga las skills desde ~/.claude/skills (todos los proyectos) o .claude/skills (un proyecto) y usa una skill cuando su descripción coincide con la tarea.
¿Qué clientes pueden usar la skill isolated-setup-install?
Cualquier cliente que lea el formato Agent Skills: Claude Code, Codex, Gemini CLI y claude.ai (subir como ZIP). Los scripts de la skill se ejecutan solo donde el cliente permite la ejecución de código.
¿Modificará mis archivos de configuración de la shell?
El SKILL no editará los archivos rc de la shell sin tu aprobación. Te mostrará la línea exacta que debes añadir y te pedirá que la pegues tú mismo.
¿Qué pasa si ya tengo configurados los ajustes de Claude?
El SKILL no sobrescribirá silenciosamente la configuración existente. Realiza un diff entre la fusión deseada y tu archivo actual, y solicita tu aprobación explícita antes de escribir.