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.
git clone --depth 1 https://github.com/iliaal/ccc-pluginWrote 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/plugins/iliaal/ccc-plugin/ccc-tools)<a href="https://agentmods.dev/plugins/iliaal/ccc-plugin/ccc-tools"><img src="https://agentmods.dev/badge/plugins/iliaal/ccc-plugin/ccc-tools/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/plugins/iliaal/ccc-plugin/ccc-tools"><img src="https://agentmods.dev/badge/plugins/iliaal/ccc-plugin/ccc-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ccc-tools 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
{
"name": "ccc-tools",
"version": "0.1.0",
"description": "Claude Code integration for cocoindex-code (ccc). Slash commands for onboarding, reset, and re-index; git hook installer for automatic incremental indexing; standard exclude presets that avoid common retrieval noise (tests, plans, compiled views, ML embedding data).",
"author": {
"name": "Ilia Alshanetsky",
"url": "https://github.com/iliaal"
},
"license": "MIT",
"keywords": [
"cocoindex-code",
"ccc",
"semantic-search",
"mcp",
"code-intelligence",
"retrieval",
"agent-tools"
]
}
What it installs
The manifest is a name and a version. 4 commands travel with it, and installing the plugin installs all of them — 96 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 20 lines scan A d0ae7ed8a5cf
ccc-tools is a plugin published in the GitHub repository iliaal/ccc-plugin (1 stars, last pushed 6mo 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
cross-code-organizer
Inspect and organize Claude Code memories, skills, MCP servers, hooks, and project context from a local dashboard.
alive
Local, user-owned context for Claude Code. Keep your work in files you control.
brewdoc
Brewdoc - Claude Code documentation tools: doc-staleness tracking, memory-sync generator, my-claude installation docs, Markdown to PDF, publishing to brewpage.app.
llm-wiki
Build a shared Markdown knowledge base with local hybrid search and an optional evidence-linked workflow to capture task lessons, evaluate skill improvements, and apply or roll back tested changes.
membrain
Graph-based agent memory — search, trace, and manage what your agent knows.
capture
Capture session information into a staging file for later reflection and knowledge graph processing.