← Files Atbash SafetyARCHIVED FILE
skills/atbash-setup/SKILL.md
4.44 KB · Nov 20, 2026 · 06:51 UTC
---
name: atbash-setup
description: Set up, connect, verify, or switch the local Atbash agent used for explicit safety checks. Use for Atbash signup, existing-agent connection, setup progress, or local profile troubleshooting.
---
# Atbash Setup
Run the bundled helper yourself in a local desktop thread. It requires Node.js 22.13.0 or newer on macOS arm64, Linux x64/arm64 with glibc, or Windows x64. Resolve `<skill-directory>` to the directory containing this file; use its installed launcher throughout a job. If local execution is unavailable, explain that this package requires a local desktop thread.
## Onboard an agent
```text
node <skill-directory>/scripts/atbash-control.mjs setup start --host codex
```
The helper uses the `codex` host profile namespace in both ChatGPT desktop and Codex. Show the returned `verificationUri` and code. The user signs in and verifies their wallet in Connect Atbash. Keep the job ID to resume the same job. Ask only for missing choices and browser approval; perform helper commands and plan-file creation yourself.
Run `setup inspect <job-id>` through the same launcher after wallet verification. Follow `nextAction`:
- `OPEN_BROWSER`: wait for the user to verify their wallet at the returned URL.
- `PREPARE_PLAN`: use discovery and user-provided choices to create a non-secret JSON file with an `actions` array. Submit it with `setup plan <job-id> --input <path>`.
- `REVIEW_IN_BROWSER`: show the verification URL; the user reviews and signs the exact proposal. Do not approve or sign for them.
- `WAIT`: inspect again after two seconds, keeping the user informed. Stop on expiry or terminal failure; do not repeatedly create new sessions.
- `ACTIVATE`: run `setup continue <job-id>` to decrypt the key locally and select the agent profile.
- `RECOVER`: report completed and failed steps. Further mutations require a new authorization session.
- `DONE`: run `node <skill-directory>/../../runtime/public-safety.cjs status`. Report whether the agent is ready for explicit safety checks.
A new-agent plan uses `create_account` and `create_organization` when missing, `activate_free_plan` if needed, then one `create_agent` with `keySource: "generate_in_browser"`. Include `network`, `organization`, `name`, `purpose`, and `risk` (`low`, `medium`, `high`, or `critical`) from discovery and the user's choices. Account actions have only `type` and `network`; organization creation uses `name` and `description`. Free-plan activation uses `organization` and requires the public network.
Suggest `policy: {"preset":"developer","version":1}` for coding, `devops` for operations, or `full_baseline` when the user requests the strictest protection. Explain the suggestion before approval; the user can choose a different preset or customize the policy in Connect Atbash.
If an existing organization needs a subscription, run `setup checkout <job-id> --organization <name>` and show the returned checkout URL. The user selects the plan and handles payment in their browser. Resume inspection afterward.
## Connect an existing agent
After wallet verification and discovery, run `profile connect <job-id>` through the launcher. Show the returned loopback `localUri`. The user enters their key only in that local form; the helper verifies that its public identity belongs to the verified wallet. Wait for the helper's completion, then run the status command above.
Never ask for, read, print, or put an agent private key in the conversation, tool arguments, environment assignments, or plan files. Credential and pending-session files are private. A browser verification URL and job ID may be shown; session secrets may not.
## Profiles and troubleshooting
Use the same launcher for `profile list --host codex`, `profile switch --host codex --profile <id>`, and `profile disconnect --host codex`. Disconnecting retains the stored credential and does not revoke the on-chain agent. After switching, run status again. Resolve an environment mismatch by connecting an agent belonging to the service reported by `public-safety.cjs help`; do not copy keys between environments.
Report helper failures without exposing credential contents or requesting backend credentials. If a local environment override conflicts with a profile, ask the user to correct it locally without revealing its value.
This package checks only explicitly submitted actions. Agent readiness does not mean other tool calls are automatically intercepted. After setup, use `$atbash-safety` when the user requests an action check.
SHA-256: 987152f634fc01288568848ef91a34951f1b22294eb2adb506ac7e8dd1728217