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.
npx agentmods add skills/zebbern/agent-collab/cursor-cli-runtimenpx skills add zebbern/agent-collab --skill cursor-cli-runtimegit clone --depth 1 https://github.com/zebbern/agent-collabWhat 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 | $0.00017 | $0.00774 |
| Opus 5 | $0.00009 | $0.00387 |
| Sonnet 5 | $0.00003 | $0.00155 |
| Haiku 4.5 | $0.00002 | $0.00077 |
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 2d 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-agentCLI strings, 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.
- Leave the model unset by default (Cursor routes
autoserver-side). Add--modelonly when the user explicitly asks for one, and pass the name through unchanged. - If the forwarded request names a task profile (
--profile deepor--profile fast), pass--profile <name>through totaskunchanged and strip it from the task text, mirroring how--modelis handled. An explicit--modeloverrides the profile's model — pass both through and lettaskresolve which wins. - There is no
--effortflag: Cursor encodes depth in model names (for examplegpt-5.3-codex-high,claude-opus-5-thinking-high) or in thedeep/fasttask profiles. If the user asks for more or less depth, choose via--modelor--profile, not an effort flag. - Default to a write-capable Cursor run by adding
--writeunless the user explicitly asks for read-only behavior or only wants review, diagnosis, or research without edits.
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 <name>, pass it through totaskand strip it from the task text. - If the forwarded request includes
--profile <deep|fast>, pass it through totaskand strip it from the task text. - If the forwarded request includes
--resume <chat-id>, pass it through totaskand strip it from the task text. Cursor resume always needs the explicit chat id — there is no resume-last shortcut. - Without
--resume, every rescue is a fresh Cursor session.
Safety rules:
- Default to write-capable Cursor work in
cursor:cursor-rescueunless the user explicitly asks for read-only behavior. - 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.
- 2d ago First seen · 40 lines · 17 tokens per session scan A 2a83851ac43f
cursor-cli-runtime is a skill published in the GitHub repository zebbern/agent-collab (32 stars, last pushed 17d ago), licensed Apache-2.0. It adds 17 tokens to every session and 774 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-30.
Other skills, from other repositories
vitest-testing
Vitest unit and integration testing patterns, commands, mocking (vi.mock), and coverage. Use when writing .test.ts files, configuring the test runner, or adding coverage thresholds.
turborepo-monorepo
Configure pipelines, set up local/remote caching, and run scoped tasks in a Turborepo monorepo. Use when you say: 'enable remote caching', 'optimize pipeline inputs/outputs', or 'filter builds to affected packages'.
decomposition
Resolves task dependencies, generates machine-actionable delegation specs, structures phased subtask plans for multi-agent work. Use when writing delegation specs, resolving task dependencies, building phased subtask plans for multi-agent work, assigning work to sub-agents, or partitioning a feature into…
linear-task-management
Creates and names Linear issues, assigns labels and priorities, manages status transitions, and links issues to PRs. Use when decomposing features into tasks or resuming interrupted sessions. Trigger terms: tickets, backlog, task breakdown, project board, sprint planning.
nx-workspace
Run and generate NX targets, configure project.json, and visualize dependency graphs. Use when you say: 'run affected tests', 'nx generate a library', 'configure project.json', or 'show dependency graph'.
trello-task-management
Create and manage Trello cards, checklists, and boards for kanban workflows. Use when the user says: 'create a kanban board', 'add a task card', 'move card to sprint', or 'track project board'.