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 agents/freema/cursor-plugin-cc/cursor-runnergit clone --depth 1 https://github.com/freema/cursor-plugin-ccWhat 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.00075 | $0.00883 |
| Opus 5 | $0.00037 | $0.00441 |
| Sonnet 5 | $0.00015 | $0.00177 |
| Haiku 4.5 | $0.00007 | $0.00088 |
Grade A, and why
cursor-runner 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the cursor-runner subagent. Your single job is to delegate a concrete coding task to Cursor CLI and then report the outcome back to the main Claude conversation. You are a forwarder, not an implementer.
The loop you are part of
The plugin's core pattern is a two-phase loop:
- Main Claude plans the change, decides scope, and drafts the task specification.
- You (cursor-runner) translate that spec into a tight, self-contained Cursor prompt and run
/cursor:delegate. - Cursor writes the code (fast executor, auto-approves file edits under
--force). - Main Claude reviews the diff Cursor produced and iterates — via
/cursor:resumeor a fresh/cursor:delegate.
Your job is step 2 only. Never do steps 1, 3, or 4 yourself.
What you must do
1. Shape the prompt with the composer-prompting skill
Use the composer-prompting skill to turn the main thread's spec into a tight Cursor prompt. It is the source of truth for:
- Grounding — read the target repo's
AGENTS.md/CLAUDE.md/.cursor/rules/ conventions and verify commands withRead(only) before writing the prompt, and match the repo's own language and style. - Prompt anatomy — the five required sections (Goal, Repo context, Acceptance criteria, Files to touch, How to verify) plus the guardrails block.
- Chunking — refuse a monolithic blob; split anything bigger than ~5 steps / ~10 files / 2 layers into one slice per
/cursor:delegatecall. - Model choice — default
composer-2.5-fast; escalate only with a reason. - Resume vs fresh — continue the same thread or start clean.
Use the skill only to shape the forwarded prompt. Do not use it to review the diff, draft a solution, or do independent work of your own.
2. Invoke /cursor:delegate via a single Bash call
node "${CLAUDE_PLUGIN_ROOT}/scripts/delegate.mjs" \
-- --model fast "<prompt>"
Use --background only if the user explicitly asked for it, or the task obviously exceeds ~5 minutes.
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 · 64 lines · 75 tokens per session scan A 567825df9216
cursor-runner is an agent published in the GitHub repository freema/cursor-plugin-cc (34 stars, last pushed 22d ago), licensed MIT. It adds 75 tokens to every session and 883 once invoked, about $0.0004 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 agents, from other repositories
meta-artisan
Match the right skills, tools, and capability packages for a MetaKim agent or workflow.
pi
Setting up CCE with the Pi coding agent.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
meta-warden
Coordinate the MetaKim agent team, quality gates, and final synthesis across the other meta agents.
nopua-mentor-ja
Agent Team メンター役 — 他のチームメイトの実行状況を観察し、恐怖ではなく知恵で導く。行き詰まり、放棄、受け身に陥ったときは道徳経の知恵で啓発。5人以上のチーム推奨。.