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/laurigates/claude-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/laurigates/claude-plugins/code-quality-plugin)<a href="https://agentmods.dev/plugins/laurigates/claude-plugins/code-quality-plugin"><img src="https://agentmods.dev/badge/plugins/laurigates/claude-plugins/code-quality-plugin/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/laurigates/claude-plugins/code-quality-plugin"><img src="https://agentmods.dev/badge/plugins/laurigates/claude-plugins/code-quality-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
code-quality-plugin 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 8d 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "code-quality-plugin",
"version": "1.28.0",
"description": "Code review, refactoring, linting, anti-pattern detection, and static analysis",
"author": {
"name": "Lauri Gates"
},
"repository": "https://github.com/laurigates/claude-plugins",
"license": "MIT",
"keywords": [
"code-review",
"refactoring",
"linting",
"analysis",
"anti-patterns",
"ast-grep",
"security",
"documentation",
"adr",
"prd",
"prp",
"quality-check",
"dry-consolidation",
"duplication",
"silent-degradation",
"preconditions",
"error-handling",
"error-swallowing",
"dead-code",
"dependency-audit",
"test-quality",
"complexity",
"supply-chain"
],
"hooks": "./hooks.json"
}
What it installs
The manifest is a name and a version. 17 skills travel with it, and installing the plugin installs all of them — 686 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill ast-grep-search A 40 tokens
- Skill bulk-sweep-classify A 51 tokens
- Skill code-antipatterns A 45 tokens
- Skill code-docs-quality A 50 tokens
- Skill code-hidden-failures A 45 tokens
- Skill dry-consolidation A 36 tokens
- Skill code-complexity A 37 tokens
- Skill code-lint A 43 tokens
- Skill debugging-methodology A 41 tokens
- Skill code-license-position A 33 tokens
- Skill code-test-quality A 35 tokens
- Skill code-dead-code A 38 tokens
- Skill code-dep-audit A 35 tokens
- Skill code-review-checklist A 38 tokens
- Skill code-scaffold-backport A 42 tokens
- Skill code-review A 38 tokens
- Skill code-refactor A 39 tokens
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.
- 8d ago Changed 5292e812df8d
- 16d ago Changed 351bba36c8a2
- 19d ago Changed b433923dbbb9
- 27d ago Changed 56798f193766
- 28d ago Changed 576259811756
- 1mo ago Changed 1bee35ed772d
- 1mo ago Changed 9b6f8f904317
- 1mo ago Changed 08fae8e716d3
- 1mo ago First seen · 38 lines scan A aea5d7c5e9c7
code-quality-plugin is a plugin published in the GitHub repository laurigates/claude-plugins (59 stars, last pushed today), 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-09-03.
Other plugins, from other repositories
codebase-health
Repo-wide drift audit between docs, config, code, and architecture: verifies every factual claim against reality via parallel subagent fan-out, severity-rates findings, and reports read-only, delegating remediation to the implementation/verification lanes. Audit dimensions are configurable through a tracked…
complexity-reducer
Reduce cyclomatic complexity and simplify functions.
double-check
Verify code correctness with systematic second-pass analysis.
code-review
Perform a comprehensive code review of recent changes.
graph-it-live
Dependency, call-graph, impact, and architecture analysis for codebases.
knowledge-virtuoso
6 knowledge skills: accessibility, context engineering, debugging, docs lookup, performance, and security.