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/sigistry/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/sigistry/marketplace/test-generator)<a href="https://agentmods.dev/plugins/sigistry/marketplace/test-generator"><img src="https://agentmods.dev/badge/plugins/sigistry/marketplace/test-generator/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/sigistry/marketplace/test-generator"><img src="https://agentmods.dev/badge/plugins/sigistry/marketplace/test-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
test-generator 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 5d 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": "test-generator",
"version": "1.0.0",
"description": "Comprehensive test generation and analysis plugin that automates test creation, identifies coverage gaps, and improves test quality across your entire codebase",
"author": {
"name": "Sigistry Test Generator",
"url": "https://github.com/Sigistry/marketplace/tree/main/plugins/test-generator"
},
"license": "MIT"
}
What it installs
The manifest is a name and a version. 5 commands travel with it, and installing the plugin installs all of them — 70 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.
- 5d ago First seen · 11 lines scan A 3d9687374800
test-generator is a plugin published in the GitHub repository sigistry/marketplace (3 stars, last pushed 4d 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-09-03.
Other plugins, from other repositories
lsa
Living Spec Architecture — a technology-agnostic spec layer that authors a grounded spec and verifies it before and after an external implementer builds it. LSA is NOT the implementer: any coding agent (Claude Code, Cursor) or human writes the code. Skills: discover (extract intent + gather codebase facts; the…
green-gate-never-examined-the-case
A check reported clean without examining the case it exists for — "green" meant "nothing ran". Use when about to trust a gate, test or CI step you have never watched fail; when a guard is green but the bug it guards shipped anyway; when a check passes on a shallow clone, a disabled object, a malformed input or an…
ab-harness
Counterfactual A/B + layered-ablation harness for Claude Code setup. Measures whether your /.claude/ stack (skills, lessons, axioms, memory) plus in-repo discipline (docs/runbooks, decisions, findings) actually helps on real tasks. Binary A/B (setup-ON vs setup-OFF) and layered ablation (strip one layer at a time, ran.
test-effectiveness-auditor
Quantitatively measure how effective a project's automated test suite is at catching real bugs, by replaying historical incidents at pre-fix commits and classifying CI failure history.
overheid-plugins marketplace
Plugin marketplace listing 7 plugins: standaarden, zad-actions, developer-overheid, nerds, internet.
f5-framework
F5 Framework - AI-powered development framework with quality gates, TDD support, and enterprise-grade tooling for Claude Code.