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/dryvist/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/dryvist/claude-code-plugins/code-standards)<a href="https://agentmods.dev/plugins/dryvist/claude-code-plugins/code-standards"><img src="https://agentmods.dev/badge/plugins/dryvist/claude-code-plugins/code-standards/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/dryvist/claude-code-plugins/code-standards"><img src="https://agentmods.dev/badge/plugins/dryvist/claude-code-plugins/code-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
code-standards 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 11d 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": "code-standards",
"version": "6.3.0",
"description": "Estate-specific code conventions not covered by generic review skills: logging format, monitoring-vs-test philosophy, doc format",
"author": {
"name": "JacobPEvans"
},
"license": "MIT",
"repository": "https://github.com/JacobPEvans/claude-code-plugins",
"keywords": [
"code",
"quality",
"review",
"testing",
"documentation",
"standards"
],
"skills": [
"./skills/code-quality-standards"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 30 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.
- 11d ago Changed be6e43d9164e
- 23d ago Changed · -1 lines 8d08d2266f42
- 1mo ago Changed 051935d30e6a
- 1mo ago Changed 0d696845921d
- 1mo ago Changed 4e1abd7349fd
- 1mo ago Changed c1331832c461
- 1mo ago First seen · 23 lines scan A 4a77675c988e
code-standards is a plugin published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed yesterday), 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
fakoli-plugin-critic
Five specialist critic agents for Claude Code plugin development — agent-critic (frontmatter/color/tools), skill-critic (lazy-loading/no-fuzzy-detection), hook-critic (contract-aware/${CLAUDEPLUGINROOT}), mcp-critic (schema/actor-validation), structure-critic (manifest/CHANGELOG/version-sync). Audit any plugin (your.
claude-code-kit
Turn any task into production-ready code. Rules and skills work on any coding harness; specialized agents and automatic hook enforcement are a Claude Code deepening feature.
rad-code-review
The specialist lanes and memory that the built-in /code-review doesn't have. Invokes the built-in engine for general bug-finding (quick/standard/deep map to its effort levels), then adds what it lacks: a mechanical hallucinated-imports validator (lockfile-verified across Python/JS/TS/Rust/Go, with a vendored denylist…
nah
NAH, Not Another Harness: ticket-driven build loop with cross-vendor code review (architect session, tk tickets, one-ticket-at-a-time developer subagent, GPT reviewer via pi).
skills-toolkit
Five commands for GitHub skills in Cowork: load from any repo, save iterated versions, share installed skills, sync updates, and auto-detect pasted URLs.
sonu
Make your coding agent work like a senior teammate instead of an eager intern. /sonu:build writes every change in your style and test-first, then hands it back with the riskiest parts flagged before you review. /sonu:ship takes it from working tree to merged PR on its own — collecting every AI reviewer bot enabled on…