Update to Atbash Safety

{
  "description": "Prepare and obtain browser approval for a change to an existing Atbash agent's name, purpose, risk, or active state.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 208
    },
    {
      "relative_path": "scripts/atbash-control.mjs",
      "size_in_bytes": 551
    }
  ],
  "name": "atbash-manage",
  "skill_md_contents": "---\nname: atbash-manage\ndescription: Prepare and obtain browser approval for a change to an existing Atbash agent's name, purpose, risk, or active state.\n---\n\n# Atbash Management\n\nUse Node.js 22.13.0 or newer in a local desktop thread. Resolve `<skill-directory>` to this file's directory and run:\n\n```text\nnode <skill-directory>/scripts/atbash-control.mjs manage start --host codex\n```\n\nShow the returned verification URL and code. After the user verifies their wallet, run `manage inspect <job-id>` through the same launcher. Use discovery to identify the exact agent and organization; clarify an ambiguous target.\n\nCreate a non-secret plan file with exactly one `update_agent` action:\n\n```json\n{\n  \"actions\": [\n    {\n      \"type\": \"update_agent\",\n      \"network\": \"public\",\n      \"organization\": \"<discovered organization>\",\n      \"agentPubkey\": \"<discovered public key>\",\n      \"changes\": { \"purpose\": \"<user-requested purpose>\" }\n    }\n  ]\n}\n```\n\nUse the discovered network and identity. Include only requested fields in `changes`: `name`, `purpose`, `risk` (`low`, `medium`, `high`, `critical`), or `active` (boolean). Submit with `manage plan <job-id> --input <path>` through the launcher.\n\nThe user reviews and signs the exact change in Connect Atbash. Never click approval controls or sign for them. A prior setup or management authorization does not authorize a new change. Inspect the job after approval; when execution is complete, run `manage continue <job-id>` and report its result. A management completion requires no new agent key or profile activation. On partial completion, report completed and failed steps; further changes need a new session and approval.\n\nUse `manage cancel <job-id>` when the user asks to cancel. Stop on expiry or terminal failure. Do not create replacement mutation sessions without the user's intent to continue.\n\nPolicy editing, billing, ownership transfer, key recovery, and certification use their dedicated dashboard flows. Never read, print, transmit, or request an agent private key.\n"
}