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/DennisLiuCk/claude-plugin-marketplaceWrote 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/dennisliuck/claude-plugin-marketplace/legacy-analyzer)<a href="https://agentmods.dev/plugins/dennisliuck/claude-plugin-marketplace/legacy-analyzer"><img src="https://agentmods.dev/badge/plugins/dennisliuck/claude-plugin-marketplace/legacy-analyzer/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/dennisliuck/claude-plugin-marketplace/legacy-analyzer"><img src="https://agentmods.dev/badge/plugins/dennisliuck/claude-plugin-marketplace/legacy-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
legacy-analyzer 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What it installs
The manifest is a name and a version. 3 commands travel with it, and installing the plugin installs all of them — 58 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 · 9 lines scan A 208138949044
legacy-analyzer is a plugin published in the GitHub repository DennisLiuCk/claude-plugin-marketplace (27 stars, last pushed 7mo ago), with no licence file. 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-30.
Other plugins, from other repositories
code-reviewer
Code review persona with comprehensive analysis capabilities.
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…
han-research
Pre-planning knowledge-work skills for the Han suite: understanding a problem before anyone commits to a plan. Home of research (research an open-ended question and end at an adversarially-validated recommendation), gap-analysis (compare two artifacts and report what is missing, incomplete, or conflicting), and…
review
Deep code review driven by a short interview: read-only reader agents per angle, verified findings, and each point routed to ship, issue, brief or propose.
scriptorium
An agentic scriptorium for scholarly writing — coordinated AI capabilities (citation audit, reviewer simulation, structural analysis) around shared editorial state.
notabene
Turnkey docs review: set up notabene on any repo — write the config, create the .notabene store, and start the review server via npx (no toolchain to install) — then run the human↔agent loop: process browser comments on your docs, apply the feedback, mark resolved, write the journal, and verify.