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/result)<a href="https://agentmods.dev/commands/freema/cursor-plugin-cc/result"><img src="https://agentmods.dev/badge/commands/freema/cursor-plugin-cc/result/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/result"><img src="https://agentmods.dev/badge/commands/freema/cursor-plugin-cc/result.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.00015 | $0.00104 |
| Opus 5.5 | $0.00006 | $0.00042 |
| Sonnet 5.5 | $0.00003 | $0.00021 |
| Haiku 4.5 | $0.00002 | $0.00010 |
Grade A, and why
result 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/result.mjs" -- "$ARGUMENTS"
Show the result block to the user as-is. Do not truncate or summarise — the user invoked this command specifically to see the full summary. End by noting the cursor-agent --resume=… line if present.
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 · 10 lines · 15 tokens per session scan A 7f15e63e19ab
result is a command published in the GitHub repository freema/cursor-plugin-cc (36 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 104 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
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
ccc-orchestrate
Run a sequential multi-agent workflow (feature, bugfix, refactor, security or custom chain) with structured handoffs, plus optional tmux and worktree workers for long-running sessions. Use when a task needs planner, implementer and reviewer stages in order.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
ccc-audit
Audit the current project for dependency vulnerabilities, oversized bundles, type errors, dead code, hardcoded secrets, undocumented env vars and a missing CLAUDE.md. Use when you want a health score before a release or review.
code-locate
Locate code paths and line ranges for a described behavior: up to 10 candidates with HIGH/MEDIUM/LOW confidence and a search trail, plus a proposed SOURCEOFTRUTH.md update. Use when the first question is where one specific behavior lives and paths are unknown. Do not use when paths are explicit, the codebase is tiny…
harvest-session-learnings
Scan the session and task artifacts for reusable lessons (what was tried, what failed and why, what surprised us) and propose entries to append to LEARNINGS.md, the produce-side counterpart to what task-init reads. Use on demand mid-task after a hard-won fix or surprising failure, or at closure to sweep a long…