# Install the Run402 skill — agent router

This page is for the agent. The complete human instruction is:

Please install the run402.com skill.

Do not ask the human for a different skill name, bootstrap URL, runtime target, or terminal command.

Route by current context

1. If this is a managed Buzz conversation, the workspace is ~/.buzz, or the released Buzz sidecar/context is present, select `run402-buzz`. In that context the sentence is the complete install-and-connect request, not a files-only request. Read https://run402.com/buzz/install.txt and follow its managed-workspace installation, truthful receipt, and same-turn continuation contract.
2. Otherwise select the ordinary `run402` skill from https://run402.com/.well-known/agent-skills/index.json and install it for only the runtime(s) actually present in the current workspace.
3. Do not install both skills speculatively. `run402-buzz` is the complete managed-Buzz package and must not be shadowed by a generic runtime-global `run402` skill.

First-party execution shape

Run the current supported generic installer yourself from the applicable workspace. Prefer passing the working directory, child-process environment, and command separately:

working_directory: <applicable-workspace>
environment: { "DO_NOT_TRACK": "1" }
command: npx --yes skills@latest add https://run402.com -s <run402-buzz-or-run402> -a <actual-runtime-target...> -y

Do not send POSIX `NAME=value command` syntax to Windows. If only a shell string is available, use `DO_NOT_TRACK=1 npx ...` in POSIX sh/Bash/zsh, `$env:DO_NOT_TRACK = '1'; npx ...` in PowerShell, or `set "DO_NOT_TRACK=1" && npx ...` in cmd.exe.

Use `claude-code` for Claude Code, `codex` for Codex, `goose` for Goose, and `universal` only for a confirmed `.agents/skills` consumer. Do not use `-a claude`. Do not ask the human to run this command.

Report only verified installation evidence: selected skill, source class, runtime target(s), workspace-relative installed path(s), and the exact digest from the first-party discovery entry. The file-copy stage is inert; it grants no authority and does not itself set up an identity, organization, project, payment, or deployment.

Managed Buzz continuation

After verification, read the installed run402-buzz SKILL.md directly from the verified workspace path and follow it immediately in this same turn. Do not stop at the installation receipt, do not say it will be available on the next turn, and do not ask whether the human wants Run402 set up. Converge any missing or pre-4.17.2 user-global Run402 CLI agent-side, verify the actual executable, and rerun the complete zero-mutation preflight before trusting its relay semantics. Continue through setup and independent public identity-link verification until the skill presents one contextual demo for approval.

Stop after the inert receipt only when the human explicitly requested files only or explicitly said not to set up or connect Run402. Deployment and human adoption still require their own later approvals.