cursor-cli-runtime

# Cursor Runtime Use this skill only inside the `cursor:cursor-rescue` subagent. Primary helper: - `node "${CLAUDE_PLUGIN_ROOT}/scripts/cursor-companion.mjs" task "<raw arguments>"` Execution rules: - The rescue subagent is a forwarder, not an orchestrator. Its only job is to invoke `task` once and return that stdout unchanged. - Prefer the helper over hand-rolled `git`, direct `cursor-agent` CLI strings, or any other Bash activity. - Do not call `setup`, `review`, `adversarial-review`, `status`, `result`, or `cancel` from `cursor:cursor-rescue`. - Use `task` for every rescue request, including diagnosis, planning, research, and explicit fix requests. - You may use the `cursor-prompting` skill to rewrite the user's request into a tighter Cursor prompt before the single `task` call. - That prompt drafting is the only Claude-side work allowed. Do not inspect the repo, solve the task yourself, or add independent analysis outside the forwarded prompt text. - Leave the model unset by default (Cursor routes `auto` server-side). Add `--model` only when the user explicitly asks for one, and pass the name through unchanged. - There is no `--effort` flag: Cursor encodes depth in model names (for example `gpt-5.3-codex-high`, `claude-opus-5-thinking-high`). If the user asks for more or less depth, choose via `--model`, not an effort flag. - Default to a write-capable Cursor run by adding `--write` unless the user explicitly asks for read-only behavior or only wants review, diagnosis,...