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 freema/cursor-plugin-cc/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/commands/freema/cursor-plugin-cc/from-plan)<a href="https://agentmods.dev/commands/freema/cursor-plugin-cc/from-plan"><img src="https://agentmods.dev/badge/commands/freema/cursor-plugin-cc/from-plan/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/commands/freema/cursor-plugin-cc/from-plan"><img src="https://agentmods.dev/badge/commands/freema/cursor-plugin-cc/from-plan.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.00023 | $0.00550 |
| Opus 5.5 | $0.00009 | $0.00220 |
| Sonnet 5.5 | $0.00005 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
from-plan 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
!node "${CLAUDE_PLUGIN_ROOT}/scripts/from-plan.mjs" -- "$ARGUMENTS"
Render the output verbatim. The command has two modes:
- Preview + hand back (default): it writes the task file, then prints the exact
/cursor:delegate @…command. Run that command yourself after reviewing the task file. - Auto-delegate (
--delegateor--yes): it writes the task file AND immediately calls/cursor:delegate, so the output merges into a single flow.
Without arguments it picks the newest plan under ~/.claude/plans/. Pass a name fragment (e.g. dark-mode) or any path (e.g. PRPs/dark-mode.md) to pick a specific one. --list shows the 15 most recent plan files.
Where the task file lands — derived from the spec, most- to least-specific:
--out-dir <dir>for a single run- the directory the source spec lives in — pass
PRPs/018.mdand the task file joins it there, in whichever repo that is - the
CURSOR_PLUGIN_CC_TASKS_DIRenvironment variable - the per-repo default:
/cursor:setup --tasks-dir PRPs(reset with--no-tasks-dir) tasks/
Rule 2 means spec-driven projects need no configuration, and it keeps working when specs are centralised in one repo while code lives in siblings. Rules 3–5 only come into play for Claude's own plan-mode files, which have no project location to inherit. Relative values resolve against the repo root, so the destination does not move when you run the command from a subdirectory.
The spec may live outside the current repo. When it does, Cursor is handed an absolute path instead of @path (which cannot leave the repo root), and told to apply its changes in the current repository. Report that note to the user when it appears.
--in-place skips the conversion entirely and delegates the source document as written — no task file is created. Use it when your spec already is the task (PRP, Spec Kit, OpenSpec). Works across repos.
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 · 29 lines · 23 tokens per session scan A 53a052a8de27
from-plan is a command published in the GitHub repository freema/cursor-plugin-cc (36 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 550 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-30.
Other commands, from other repositories
taskstoissues
A command that turns structured tasks from project design documents into ordered GitHub Issues, written in simplified Chinese.
ijfw-status
Show IJFW state -- mode, routing, memory, recent activity, codebase index, settings. Use when you want the at-a-glance banner you'd otherwise get at session start.
team
Manage your project's agent team. Usage: /team [setup|list|add|remove|swap].
workflow
Start or resume the IJFW project workflow. Usage: /workflow [discover|plan|execute|verify|ship|status].
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.
implementation-plan
Define an incremental plan for the active task as IMPLEMENTATIONPLAN.md plus a TASKSTATE.md update: smallest safe slices with scope, validation and exit criteria. No code is written. A --spec mode derives slices from a spec or PRD. A retrofit mode annotates in-progress plans so they can adopt implement-fleet. Do not…