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.
/plugin marketplace add ningzio/cursor-plugin-ccnpx agentmods add plugins/ningzio/cursor-plugin-cc/marketplacegit clone --depth 1 https://github.com/ningzio/cursor-plugin-ccGrade A, and why
cursor-plugin-cc 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 yesterday.
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
{
"name": "cursor-plugin-cc",
"owner": {
"name": "ningzio",
"url": "https://github.com/ningzio"
},
"metadata": {
"description": "Dispatch tasks to cursor-agent from Claude Code. In-place by default; --isolated opts into a sandbox worktree. Background jobs, session boundary safety, structured policy refusals.",
"homepage": "https://github.com/ningzio/cursor-plugin-cc",
"version": "0.3.0"
},
"plugins": [
{
"name": "cursor",
"source": "./plugins/cursor",
"version": "0.3.0",
"description": "Six slash commands (/cursor:setup, /cursor:dispatch, /cursor:status, /cursor:result, /cursor:cancel, /cursor:cleanup) that hand a task off to cursor-agent. Default is in-place (edits the caller's cwd); --isolated runs in a sandbox worktree with auto-commit. Background jobs with full job control, per-Claude-session filtering, and structured policy refusals (`REFUSED: <CODE>`) suitable for autonomous callers.",
"category": "agent",
"tags": ["cursor", "cursor-agent", "agent", "worktree", "background-jobs", "delegation"]
}
]
}
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.
- yesterday First seen · 23 lines scan A 4085ae2913de
cursor-plugin-cc is a plugin published in the GitHub repository ningzio/cursor-plugin-cc (2 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.
Other plugins, from other repositories
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.