GITHUB_REPOS=<fill-this-in>

Set up Cursor Agent SDK on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/cursor-agent-sdk.md from top to bottom.

The values at the top of this message are mine:
- GITHUB_REPOS: the GitHub repositories to review, as owner/name, comma-separated, all with the same owner and already connected to Cursor
Ask me for any that still say <fill-this-in> before you need them.

The recipe's example VM name is my-cursor-agent. This VM's name is the output of `hostname`: use it wherever the recipe writes my-cursor-agent. Skip the step that creates the VM; you are on it.

You are done when all of these are true. Check each one yourself:
- The Agent SDK CLI 0.4 on Node.js 24, and Cursor's security-reviewer template in ~/security-reviewer, a git repository that watches GITHUB_REPOS
- The VM signed in to Cursor (`agent-sdk whoami` names the account), with no GitHub token on it
- security-reviewer.service enabled, so it comes back after a reboot, with state in ~/agent-state
- The playground answering at `https://<vm>.exe.xyz:3000/playground`, private to the VM's owner
- Both smoke evals passing with `agent-sdk eval`

Run "Install by hand" first, skipping VM creation; the walkthrough is for
the owner afterwards. Use GITHUB_REPOS exactly as given. For "Sign in to
Cursor", start `agent-sdk login` in a tmux session, give the owner the
URL it prints, and wait until `agent-sdk whoami` names an account; never
ask for, print, or copy an API key. Don't open, comment on, or review
pull requests yourself, and don't run `agent-sdk deploy`. Keep port 3000
private: never run share set-public or share port. Finish with
https://<vm>.exe.xyz:3000/playground, using this VM's name, and point the
owner to "Review a pull request".

Finish with the URLs I should open.