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 lollipopkit/cc-pluginsnpx agentmods add plugins/lollipopkit/cc-plugins/context-firewallgit clone --depth 1 https://github.com/lollipopkit/cc-pluginsGrade A, and why
context-firewall 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": "context-firewall",
"version": "0.1.0",
"description": "Context Firewall: use sub-agents to preprocess large inputs with evidence contracts and low-cost verification.",
"author": {
"name": "lollipopkit"
},
"keywords": [
"context",
"sub-agent",
"summarization",
"evidence",
"verification",
"map-reduce"
],
"repository": "https://github.com/lollipopkit/cc-plugins",
"license": "MIT",
"commands": "./commands/"
}
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 · 20 lines scan A f4a597175a92
context-firewall is a plugin published in the GitHub repository lollipopkit/cc-plugins (7 stars, last pushed 5mo 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
paperthin
Low-level agentic design patterns. Turning old engineering wisdom into reflexes your agent reaches for on its own—on any agent.
rune-kit
Less skills. Deeper connections. A lean, interconnected skill ecosystem for Claude Code — 66 skills, 248 connections, 45 signals, and runtime auto-discipline.
rune
67-skill mesh for Claude Code with runtime auto-discipline — native hooks (preflight/sentinel/completion-gate/quarantine) auto-fire at lifecycle boundaries. 248 mesh connections + 46 signals, adaptive routing, mesh analytics, MCP quarantine guidance, and project memory.
jaiskills
Orchestration (insistir, constatar, remoto), prompting (metaprompt), knowledge compounding, file-based TODOs, and OpenAI tooling (askcodex, image-to-frontend) as one Claude Code plugin.
jaiskills
Jairo's agent skills for Claude Code — orchestration, verification, prompting, and OpenAI tooling in one plugin.
askit-probe-fixtures
Plugin marketplace listing 3 plugins: probe-agents-scan, probe-collision-a, probe-collision-b.