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/qte77/claude-code-pluginsWrote 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/qte77/claude-code-plugins/cc-meta)<a href="https://agentmods.dev/plugins/qte77/claude-code-plugins/cc-meta"><img src="https://agentmods.dev/badge/plugins/qte77/claude-code-plugins/cc-meta/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/qte77/claude-code-plugins/cc-meta"><img src="https://agentmods.dev/badge/plugins/qte77/claude-code-plugins/cc-meta.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cc-meta 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 17d 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": "cc-meta",
"version": "1.16.2",
"description": "Claude Code meta-skills for cross-project synthesis, context compaction, session intelligence, and memory seed template",
"author": {
"name": "Claude Code Utils Contributors"
},
"keywords": [
"meta",
"big-picture",
"synthesis",
"context",
"compaction",
"sessions",
"plans",
"reasoning-modes"
]
}
What it installs
The manifest is a name and a version. 9 skills, 1 hook travel with it, and installing the plugin installs all of them — 328 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill synthesizing-cc-bigpicture A 50 tokens
- Skill distilling-plan-learnings A 33 tokens
- Skill mining-session-patterns A 37 tokens
- Skill orchestrating-parallel-workers A 34 tokens
- Skill cross-checking-research A 50 tokens
- Skill persisting-bigpicture-learnings A 34 tokens
- Skill handing-off-session A 26 tokens
- Skill summarizing-session-end A 35 tokens
- Skill compacting-context A 29 tokens
- Hook SessionStart A not measured
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.
- 17d ago Changed f905b2ca53bc
- 21d ago Changed 06229219b57d
- 23d ago Changed f70aea9bddac
- 1mo ago First seen · 19 lines scan A 9ffb941c97c3
cc-meta is a plugin published in the GitHub repository qte77/claude-code-plugins (3 stars, last pushed 4d ago), licensed Apache-2.0. 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
second-brain
Agentic workflow with memory and tribal knowledge. Transforms Claude from goldfish to elephant with persistent knowledge across sessions.
product-marketing-context
The PMM brain — builds and maintains /foundation/brain.md, the GTM context file every other plugin in this stack reads before producing output.
esp32-cpp
Evidence-first ESP32 firmware guidance for hardware, FreeRTOS, memory, peripherals, and field failures.
android-analysis
Android APK, AAR, and JAR decompilation and inspection toolkit for analyzing compiled binaries, unpacking libraries, and understanding obfuscated code.
android-kotlin-compose
Android development guidance with Kotlin and Jetpack Compose. MVVM architecture, state management, Navigation, Room, Hilt, and Material3 patterns.
android-kotlin-coroutines
Android development guidance with Kotlin Coroutines and Flow. Structured concurrency, StateFlow/SharedFlow patterns, lifecycle integration, testing with Turbine, and library integrations (Retrofit, Room, WorkManager).