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/harnessprotocol/harness-kitWrote 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/harnessprotocol/harness-kit/review)<a href="https://agentmods.dev/plugins/harnessprotocol/harness-kit/review"><img src="https://agentmods.dev/badge/plugins/harnessprotocol/harness-kit/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/harnessprotocol/harness-kit/review"><img src="https://agentmods.dev/badge/plugins/harnessprotocol/harness-kit/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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": "review",
"description": "Code review for a branch, PR, or path — structured output with severity labels and cross-file analysis",
"version": "0.3.0",
"category": "code-quality",
"tags": ["code-review", "pull-request", "static-analysis", "github"],
"x-developed-with": "claude-sonnet-4-6",
"requires": {
"env": [
{
"name": "GH_TOKEN",
"description": "GitHub personal access token — used by gh CLI for fetching PR diffs",
"required": false,
"sensitive": true,
"when": "Reviewing pull requests by number (e.g., /review 123)"
}
]
}
}
What it installs
The manifest is a name and a version. 1 skill, 1 agent travel with it, and installing the plugin installs all of them — 137 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 First seen · 20 lines scan A 1da24fbce817
review is a plugin published in the GitHub repository harnessprotocol/harness-kit (10 stars, last pushed today), 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
code-craftsmanship
Code quality and software design skills including Clean Code (Robert C. Martin), Refactoring patterns (Martin Fowler), A Philosophy of Software Design (John Ousterhout), The Pragmatic Programmer (Hunt & Thomas), Domain-Driven Design (Eric Evans), Working Effectively with Legacy Code (Michael Feathers), and Google's…
slopmop marketplace
Slop-mop quality gates as a Claude skill — directed remediation for AI-assisted codebases.
dotnet-backend
Pure .NET 10 backend architecture for Kestrel-hosted REST and SignalR services with DI, data access, and SOLID review.
rust
Rust code critique, architecture guidance, and idiomatic pattern enforcement.
fable-super-audit
Comprehensive, rubric-driven, whole-repository code audit that ends in a prioritized improvement plan with an executive health grade.
code-cleanup
Evidence-first cleanup of agent trajectory residue, dead islands, split-brain authority, stale dependencies, and unnecessary code across repositories.