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/smk-labs/claude-plugins/cursor-delegatenpx skills add smk-labs/claude-plugins --skill cursor-delegategit clone --depth 1 https://github.com/smk-labs/claude-pluginsWrote 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/smk-labs/claude-plugins/cursor-delegate)<a href="https://agentmods.dev/skills/smk-labs/claude-plugins/cursor-delegate"><img src="https://agentmods.dev/badge/skills/smk-labs/claude-plugins/cursor-delegate.svg" alt="Measured on agentmods" 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 | $0.00109 | $0.03247 |
| Opus 5 | $0.00055 | $0.01623 |
| Sonnet 5 | $0.00022 | $0.00649 |
| Haiku 4.5 | $0.00011 | $0.00325 |
Grade D, and why
cursor-delegate scanned grade D with 3 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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Auth (key-based, the normal path): put Cursor API keys in `~/.claude-deck/cursor/agent-keys.json` (chmod 600) and name the default account: Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- Install the CLI: `curl https://cursor.com/install -fsS | bash`. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Install the CLI: `curl https://cursor.com/install -fsS | bash`. How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegate to Cursor (agent calling)
Hand a self-contained slice to cursor-agent; it runs on the Cursor plan's quota while Claude keeps the context and the plan. This is agent calling, not a model swap: Cursor sells no Anthropic-shaped API for its subscription, so Claude's own engine can't point at it, but the two run side by side.
Pick the runner first
One measured fact drives this choice: flaky networks (VPNs especially) kill any single cursor-agent stream older than ~5 minutes. Long runs die at minute ~6 with "Connection lost" while short requests keep succeeding.
- Quick task — the worker will plausibly finish in under ~4 minutes (one focused edit, a lookup, a small test fix): call
cursor_run. - Anything else — multi-file work, builds, test loops, refactors, research that reads a lot: use the legged runner. Never start a long single stream.
Quick tasks: the cursor_run MCP tool
Call cursor_run (from this plugin) with the task:
task(required) — the self-contained instruction.account(optional) — omit it in the normal case. With no account, auth comes from thedefaultentry of~/.claude-deck/cursor/agent-keys.json(a stable API key — deterministic, no browser login involved). Pass an account name only when the user keeps several Cursor seats and names one.model(optional). Cursor meters two separate pools: first-party (auto,composer-*,cursor-*) has the large allowance; API pass-through (claude-*,gpt-*) has a small one that empties fast. Preferautofor mechanical work; spend an API-pool model on prose, judgment or review. Say which you used. Full rule: the cursor-orchestrate skill, "Model routing".extraArgs(optional) — flags passed straight to cursor-agent (e.g.["--resume", "<session_id>"]). Approval flags are not needed: every runner already passes--force --approve-mcps, so workers edit files, run shell, and use MCPs without prompting.dryRun: true— print the exact command (key redacted) without running, to show the user first.
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.
- 4d ago First seen · 102 lines · 109 tokens per session scan D d085a7db9fa1
cursor-delegate is a skill published in the GitHub repository smk-labs/claude-plugins (11 stars, last pushed 3d ago), licensed MIT. It adds 109 tokens to every session and 3,247 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
ab-test-analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go…
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
sprint-plan
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.