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/secondsky/claude-skillsWrote 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/secondsky/claude-skills/code-review)<a href="https://agentmods.dev/plugins/secondsky/claude-skills/code-review"><img src="https://agentmods.dev/badge/plugins/secondsky/claude-skills/code-review/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/secondsky/claude-skills/code-review"><img src="https://agentmods.dev/badge/plugins/secondsky/claude-skills/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
code-review 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 1mo 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-review",
"description": "Code review practices with technical rigor and verification gates. Use for receiving feedback, requesting code-reviewer subagent reviews, or preventing false completion claims in pull requests.",
"version": "3.9.0",
"author": {
"name": "Claude Skills Maintainers",
"email": "[email protected]"
},
"license": "MIT",
"repository": "https://github.com/secondsky/claude-skills",
"keywords": [
"code-review",
"code",
"review",
"tooling",
"workflow"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 35 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.
- 1mo ago Changed 29e73eeec455
- 1mo ago First seen · 19 lines scan A a4171b958dba
code-review is a plugin published in the GitHub repository secondsky/claude-skills (231 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
chamnan
Preserves repository architecture, decisions, work state, and reusable engineering context across coding-agent sessions.
fewword
Context engineering plugin - tiered offloading, smart summaries, secret redaction, TOML/JSON config, command aliases, MCP allowlists, and self-diagnostics.
review-gate
Native Claude Code AI code review + blocking pre-push gate on your Claude subscription. Isolated headless reviewer, severity/confidence verdicts, fails closed. open-code-review, done compliantly.
self-review
Review every code change before the turn ends: fresh-context reviewer agents, a verified finding standard, honest convergence, and a measured token budget — enforced by a Stop hook, graph-aware when you have a code graph, zero-cost when you don't.
architecture-review
Audits existing system architecture for anti-patterns, scalability risks, and reliability gaps. Produces graded findings with migration roadmap.
rust-intel
Defense against LLM Rust failure modes: 59 categories of bugs that survive rustc, clippy, and cargo test — async cancellation, unsafe/FFI, concurrency, crypto, supply-chain, tests-that-pass-by-luck, semantic conformance, and systemic performance cost. Ships the rust-intel skill plus /rust-intel:audit, /rust-intel:fix.