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 richer-richard/cc-researchnpx agentmods add plugins/richer-richard/cc-research/plugingit clone --depth 1 https://github.com/richer-richard/cc-researchGrade A, and why
cc-research 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "cc-research",
"version": "1.1.3",
"description": "Multi-agent deep research on Claude models: orchestrator -> parallel researcher subagents -> triangulate -> synthesize -> cite -> report. Built-in tools only (WebSearch, WebFetch, Read, Grep, Glob, Write, Task); no external research APIs or MCP servers.",
"author": {
"name": "Richard Huang"
},
"homepage": "https://github.com/richer-richard/cc-research",
"repository": "https://github.com/richer-richard/cc-research",
"license": "MIT",
"keywords": ["research", "deep-research", "multi-agent", "subagents", "citations"]
}
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 · 14 lines scan A b7f20eb72b84
cc-research is a plugin published in the GitHub repository richer-richard/cc-research (1 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
scout
Autonomous knowledge management and daily briefing system. Monitors your work tools (Slack, Calendar, Linear, GitHub, etc.), synthesizes findings into a persistent knowledge base with a formal ontology, and delivers daily action items — all running unattended via scheduled Claude Code sessions. Six session types…
scout-plugin
Marketplace for the Scout autonomous knowledge management plugin.
orbit
Plugin marketplace listing 1 plugin: orbit.
orbit
Turn any repo into a self-prompting agentic loop — a governed, project-fitted sub-agent team with persistent memory, a task/question router, hard safety brakes, a live team board, and active learning.
milestone-driver
Drives a GitHub milestone to completion: triages each issue for design gaps + dependency order up front, then for each buildable issue finds the root cause (or parks it), dispatches a TDD implementer subagent, runs unit + E2E tests + code review, opens a PR, and auto-merges issues on CI green. The whole loop sits…
milestone-driver
Plugin marketplace listing 1 plugin: milestone-driver.