Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Armert-Labs/cursor-plugin/plugin install cursorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/armert-labs/cursor-plugin/cursor-cli-runtime)<a href="https://agentmods.dev/skills/armert-labs/cursor-plugin/cursor-cli-runtime"><img src="https://agentmods.dev/badge/skills/armert-labs/cursor-plugin/cursor-cli-runtime/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/armert-labs/cursor-plugin/cursor-cli-runtime"><img src="https://agentmods.dev/badge/skills/armert-labs/cursor-plugin/cursor-cli-runtime.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00017 | $0.00782 |
| Opus 5.5 | $0.00007 | $0.00313 |
| Sonnet 5.5 | $0.00003 | $0.00156 |
| Haiku 4.5 | $0.00002 | $0.00078 |
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 1mo ago.
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.
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
taskonce and return that stdout unchanged. - Prefer the helper over hand-rolled
git, directcursor-agentstrings, or any other Bash activity. - Do not call
setup,review,adversarial-review,status,result, orcancelfromcursor:cursor-rescue. - Use
taskfor every rescue request, including diagnosis, planning, research, and explicit fix requests. - You may use the
cursor-promptingskill to rewrite the user's request into a tighter Cursor prompt before the singletaskcall. - 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:
taskis write-capable by default: Cursor runs with--forceand may edit files in the working tree.- Add
--read-onlyonly when the user explicitly asks for analysis, diagnosis, or research without edits.--read-onlymaps tocursor-agent --mode ask(read-only Q&A). - Never add a separate write flag yourself; write is the default and
--read-onlyis the opt-out.
Model selection:
- Leave the model unset by default. Add
--modelonly when the user explicitly asks for one. - The companion resolves these aliases (any concrete
cursor-agentmodel id also passes through):spark/composer->composer-2.5(fast, cheap; good for routine rescue)fast->composer-2.5-fastreview/codex->gpt-5.1-codex-max-high(strong reasoning/coding)max->gpt-5.5-highopus->claude-opus-4-8-high(Claude via Cursor, for a different model family)
Command selection:
- Use exactly one
taskinvocation per rescue handoff. - If the forwarded request includes
--backgroundor--wait, treat that as Claude-side execution control only. Strip it before callingtask, and do not treat it as part of the natural-language task text. - If the forwarded request includes
--model, pass it through totask(the companion resolves aliases). - If the forwarded request includes
--read-only, pass--read-onlytotask. - 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
taskcommand exactly as-is. - If the Bash call fails or Cursor cannot be invoked, return nothing.
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.
- 1mo ago First seen · 50 lines · 17 tokens per session scan A 4793151b30bb
cursor-cli-runtime is a skill published in the GitHub repository Armert-Labs/cursor-plugin (3 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 782 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
resolve-plugins
Curate Claude Code skill / MCP / hook picks against live upstream sources and pin them in .claude/settings.json. Adding a process harness (a paired skill set) is an ordinary pick this door handles. Reads stack from docs/techstack.md, workflow signal from docs/overview.md + existing pins, then live-queries six source…
journey-simulation
Use when caller wants to observe how a stranger encounters a flow, artifact, or sandbox — triggers like "simulate a user journey", "test our onboarding / checkout / signup", "will my ICP convert", "how does a cold reader experience this README", "first-time user test", "cognitive walkthrough", or any request to…
check-docs-consistency
Cross-reference project docs for drift, stale references, and contradictions. Outputs timestamped report. Discovers Markdown wherever it lives in the repo.
release
Prepare a version release — bump version files, commit, and tag. Just run /release with no arguments.
merge
Absorb one or more feature branches into the base branch. Recommends merge vs rebase per branch. On conflict, aborts that branch + surfaces the file list + stops. Resolution out of scope; routes to the harness-named conflict-resolution agent or the user.
release-init
Detect project type and generate a tailored project-level /release skill. Run once per project to set up releasing.