Update to Aikido Security

{
  "description": "Configures the Aikido plugin by signing the user in through the MCP login tool and verifying the MCP server. Use when the user wants to set up or verify the Aikido plugin, after installing it, when aikido mcp tool call fails or is unavailable, or when the user wants to switch Aikido accounts or re-authenticate.",
  "included_files": [],
  "name": "setup",
  "skill_md_contents": "---\nname: setup\ndescription: Configures the Aikido plugin by signing the user in through the MCP login tool and verifying the MCP server. Use when the user wants to set up or verify the Aikido plugin, after installing it, when aikido mcp tool call fails or is unavailable, or when the user wants to switch Aikido accounts or re-authenticate.\n---\n\nWhen helping the user configure the Aikido security plugin:\n\n## First: Verify Node.js version\n\nBefore doing anything else, run `node --version` to check the installed Node.js version.\n\n- If Node.js is not installed or the command fails, stop and tell the user that Node.js 18.19.0 or higher is required to run the Aikido MCP server, and direct them to https://nodejs.org to install it.\n- If the version is below 18.19.0, stop and tell the user that the Aikido MCP server requires Node.js 18.19.0 or higher, show the currently installed version, and direct them to https://nodejs.org to upgrade.\n- If the version is 18.19.0 or higher, proceed with the steps below.\n\n**If the user is asking to switch accounts or re-authenticate**, call **aikido-mcp:aikido_login** with `force_reauth: true` and skip step 1 — the tool will always return a fresh sign-in URL. Continue from step 3 to walk the user through opening the URL and step 4 to verify.\n\n**Otherwise**, follow the standard setup flow:\n\n1. Check the MCP server is reachable and the user is signed in by calling **aikido-mcp:aikido_login** with no arguments. The tool is idempotent — it returns \"Already signed in\" if a valid token is cached, otherwise it starts a new sign-in flow.\n2. If it reports the user is already signed in, confirm to the user that the Aikido plugin is configured and ready to use. Stop here.\n3. If it returns a sign-in URL, present it to the user verbatim — do not strip or modify the `state`, `redirect_uri`, or `regionRedirect` query parameters — and ask them to open it in a browser to complete sign-in. The URL automatically redirects the user to their account's region, so there is no need to pick a region. Only pass the optional `region` argument when the user explicitly names a region (e.g. EU / US / ME / AU), or when the automatic redirect sent them to the wrong one.\n4. Once the user reports they have completed the browser sign-in, verify the setup by calling **aikido-mcp:aikido_login** again.\n5. If the **aikido_login** call itself fails because the MCP server is unavailable, tell the user to ensure the Aikido plugin is installed and that the `aikido-mcp` server has been loaded, then retry.\n"
}