cursor-cli-runtime

An internal helper rule for a rescue worker that forwards one request to Cursor's command-line tool. It can pass requests for diagnosis, planning, research, or code changes.

In plain words
What is it for?
Running one Cursor task from the rescue worker, including requests that may edit files or requests limited to read-only analysis.
Why use it?
It keeps the rescue worker focused on forwarding the request instead of inspecting the repository or coordinating extra steps.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/armert-labs/cursor-plugin/cursor-cli-runtime
Any agent
npx skills add Armert-Labs/cursor-plugin --skill cursor-cli-runtime
Clone the repo
git clone --depth 1 https://github.com/Armert-Labs/cursor-plugin

Made for: Claude Code, Codex.

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 782 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00782
Opus 5 $0.00009 $0.00391
Sonnet 5 $0.00003 $0.00156
Haiku 4.5 $0.00002 $0.00078

Measured yesterday against content hash 4793151b30bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursor-cli-runtime scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/cursor/skills/cursor-cli-runtime/SKILL.md · 50 lines

What it actually says

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 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.

Write mode:

  • task is write-capable by default: Cursor runs with --force and may edit files in the working tree.
  • Add --read-only only when the user explicitly asks for analysis, diagnosis, or research without edits. --read-only maps to cursor-agent --mode ask (read-only Q&A).
  • Never add a separate write flag yourself; write is the default and --read-only is the opt-out.

Model selection:

  • Leave the model unset by default. Add --model only when the user explicitly asks for one.
  • The companion resolves these aliases (any concrete cursor-agent model id also passes through):
    • spark / composer -> composer-2.5 (fast, cheap; good for routine rescue)
    • fast -> composer-2.5-fast
    • review / codex -> gpt-5.1-codex-max-high (strong reasoning/coding)
    • max -> gpt-5.5-high
    • opus -> claude-opus-4-8-high (Claude via Cursor, for a different model family)

Command selection:

  • Use exactly one task invocation per rescue handoff.
  • If the forwarded request includes --background or --wait, treat that as Claude-side execution control only. Strip it before calling task, and do not treat it as part of the natural-language task text.
  • If the forwarded request includes --model, pass it through to task (the companion resolves aliases).
  • If the forwarded request includes --read-only, pass --read-only to task.
  • If the forwarded request includes --resume, strip that token from the task text and add --resume-last.
  • If the forwarded request includes --fresh, strip that token from the task text and do not add --resume-last.
  • task --resume-last: continues the latest Cursor task chat in this repository/session ("keep going", "resume", "apply the top fix", "dig deeper").

Safety rules:

  • Preserve the user's task text as-is apart from stripping routing flags.
  • Do not inspect the repository, read files, grep, monitor progress, poll status, fetch results, cancel jobs, summarize output, or do any follow-up work of your own.
  • Return the stdout of the task command exactly as-is.
  • If the Bash call fails or Cursor cannot be invoked, return nothing.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 50 lines · 17 tokens per session scan A 4793151b30bb

Subscribe to this mod's changes

cursor-cli-runtime is a skill published in the GitHub repository Armert-Labs/cursor-plugin (3 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 782 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens