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 gowtham012/Claude-pluginsnpx agentmods add plugins/gowtham012/claude-plugins/rubber-duckgit clone --depth 1 https://github.com/gowtham012/Claude-pluginsGrade A, and why
rubber-duck 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 2d 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": "rubber-duck",
"description": "Explain-before-you-code enforcer. Forces Claude to describe its approach in plain English and get user approval before writing any code.",
"version": "1.0.0",
"author": {
"name": "Gowtham"
},
"license": "MIT",
"homepage": "https://github.com/gowtham012/Claude-plugins/tree/main/rubber-duck",
"repository": "https://github.com/gowtham012/Claude-plugins",
"keywords": [
"explanation",
"planning",
"communication",
"approval",
"discipline"
]
}What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 18 lines scan A 35f3978e801d
rubber-duck is a plugin published in the GitHub repository gowtham012/Claude-plugins (5 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
threat-model
Produce threat models for open-source projects: the security contract between a project and its users, structured for downstream integrators and vulnerability triagers.
neatcontext
Save Claude Code work as reusable, domain-aware context.
talk-to-anyone
Turn any public figure into your personal coach, living or historical. /coach researches the person across the web, pulls real transcripts when they have video anywhere on YouTube, builds a persona, and talks to you as them until you switch or end.
dokumenty
Operacje na dokumentach: konwersja PDF/Office do Markdown (markitdown, opendataloader-pdf), redlining .docx z Track Changes (redline-docx-pl), anonimizacja i pseudonimizacja PII (let-it-be), terminy procesowe (terminy-procesowe-pl), klauzule umowne (klauzule-kontraktowe-pl), kalkulatory procesowe…
rook-claude
Claude Code plugins for rook (github.com/rook/) maintainers: maintainer-grade code review, backlog triage, systemic-PR campaigns, and rook house conventions.
rook-maintainer
Maintainer-grade skills for rook (github.com/rook/): code review, backlog triage, systemic-PR campaigns, and the rook house conventions they enforce.