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/devMappouras/local-code-review-claude-pluginWrote 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/devmappouras/local-code-review-claude-plugin/marketplace)<a href="https://agentmods.dev/plugins/devmappouras/local-code-review-claude-plugin/marketplace"><img src="https://agentmods.dev/badge/plugins/devmappouras/local-code-review-claude-plugin/marketplace/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/devmappouras/local-code-review-claude-plugin/marketplace"><img src="https://agentmods.dev/badge/plugins/devmappouras/local-code-review-claude-plugin/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
devMappouras-plugins marketplace 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": "devMappouras-plugins",
"owner": {
"name": "Christos Mappouras",
"url": "https://github.com/devMappouras"
},
"plugins": [
{
"name": "local-code-review",
"source": {
"source": "github",
"repo": "devMappouras/local-code-review-claude-plugin"
},
"description": "Local code review for uncommitted changes in .NET and Angular projects. Reviews code for bugs, security issues, and best practices. Builds .NET/Angular projects and optionally runs unit tests (NUnit/XUnit).",
"version": "1.0.0",
"author": {
"name": "Christos Mappouras",
"url": "https://github.com/devMappouras"
},
"homepage": "https://github.com/devMappouras/local-code-review-claude-plugin",
"repository": "https://github.com/devMappouras/local-code-review-claude-plugin",
"license": "MIT",
"keywords": [
"code-review",
"dotnet",
"angular",
"testing",
"nunit",
"xunit",
"clean-architecture",
"solid",
"security"
],
"category": "development"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.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.
- 1mo ago First seen · 38 lines scan A dbd710922563
devMappouras-plugins marketplace is a plugin published in the GitHub repository devMappouras/local-code-review-claude-plugin (1 stars, last pushed 10mo 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
swe-workbench
Senior-engineer toolkit: principled design (Clean Arch, DDD, SOLID, TDD, patterns, observability, concurrency), security review, language expertise (Bash, C#, Dart, Go, Java, Kotlin, Python, Ruby, Rust, SQL, Swift, TypeScript), and pragmatic workflows.
brooks-lint
AI code reviews grounded in twelve classic engineering books — decay risk diagnostics with book citations, severity labels, and six analysis modes (PR review, architecture audit, tech debt, test quality, health dashboard, full-sweep auto-fix).
brooks-lint
AI code reviews grounded in twelve classic engineering books — decay risk diagnostics with book citations, severity labels, and six analysis modes (PR review, architecture audit, tech debt, test quality, health dashboard, full-sweep auto-fix).
han-coding
Coding-facing skills for the Han suite: writing, reviewing, testing, investigating, and standardizing code. Home of the tdd skill, which drives a feature or behavior through a BDD-framed red-green-refactor loop with an enforced observed-failure gate, and the refactor skill, which restructures existing code without…
crap-analyzer
Analyze recently-changed code for Change Risk Anti-Patterns. Computes CRAP per changed function across TypeScript, JavaScript, Python, Java, Kotlin, Go, Ruby, C#, Rust, and PHP. Auto-discovers how the repo generates coverage and proposes refactors + test stubs.
vitest-auto-spy
Typed test spies from a class or a type on Vitest, bun:test and node:test — the skill teaches an agent the API, the anti-patterns, the error→fix table and the codemod that migrates a suite off jest-auto-spies or jasmine-auto-spies.