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/jimmc414/claude-code-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/jimmc414/claude-code-plugin-marketplace/adversarial-testing)<a href="https://agentmods.dev/plugins/jimmc414/claude-code-plugin-marketplace/adversarial-testing"><img src="https://agentmods.dev/badge/plugins/jimmc414/claude-code-plugin-marketplace/adversarial-testing/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/jimmc414/claude-code-plugin-marketplace/adversarial-testing"><img src="https://agentmods.dev/badge/plugins/jimmc414/claude-code-plugin-marketplace/adversarial-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
adversarial-testing 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": "adversarial-testing",
"version": "1.0.0",
"description": "Adversarial test generation that finds real bugs by inverting the reward structure",
"author": {
"name": "jimmc414",
"email": "[email protected]"
},
"homepage": "https://github.com/jimmc414/claude-code-plugin-marketplace/tree/main/plugins/adversarial-testing",
"repository": "https://github.com/jimmc414/claude-code-plugin-marketplace",
"license": "MIT",
"keywords": ["testing", "adversarial", "bugs", "mutation", "quality", "pytest"],
"category": "testing",
"dependencies": {},
"commands": "./commands/",
"agents": "./agents/",
"skills": "./skills/",
"hooks": "./hooks/hooks.json",
"mcpServers": "./.mcp.json"
}
What it installs
The manifest is a name and a version. 2 skills, 3 agents travel with it, and installing the plugin installs all of them — 176 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 · 21 lines scan A 6354610c89f6
adversarial-testing is a plugin published in the GitHub repository jimmc414/claude-code-plugin-marketplace (4 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-08-31.
Other plugins, from other repositories
implementation
Disciplined implementation stage: execute approved plans inline (/implementation:implement) or via orchestrated worker subagents (/implementation:implement-dispatch) with incremental validation, TDD-by-default cadence, green-checkpoint commits, scope-fence drift detection, and divergence detection that routes back.
evals
LLM evaluation methodology and eval-suite design, based on Anthropic's evaluation guidance. /evals:methodology answers questions on success criteria, eval design, and grading. /evals:design interviews for measurable success criteria and scaffolds a graded eval suite for an LLM app or Claude Code skill.…
mutation-testing
Measures whether a test suite can actually detect faults, not merely execute code: /mutation-testing:principles answers operator, mutant-state, and metric questions from the primary literature; /mutation-testing:setup verifies the ecosystem's mutation tool and writes the tracked config; /mutation-testing:audit ru.
playwright
Live E2E browser automation via Microsoft's @playwright/cli: named sessions, accessibility-ref snapshots, click/fill by ref, screenshots, console and network capture, mocking, tracing, video, and auth state, with artifacts written to disk so only paths enter context, plus a vendored upstream baseline and maintainer…
code-metrics
Read-only code measures for a change, with cited references and no verdict: lines per file (audit-size), cyclomatic, cognitive, and Halstead complexity (audit-complexity), duplication (audit-duplication), per-function coverage and CRAP from existing lcov, Cobertura, coverage.py, or Go artifacts (audit-coverage)…
debugging
Debug observed failures via a disciplined six-phase loop: build a fast deterministic reproduction signal, reproduce, rank falsifiable hypotheses, instrument, fix with a regression test, then clean up and post-mortem.