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/laurigates/claude-pluginsWrote 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/agents/laurigates/claude-plugins/test)<a href="https://agentmods.dev/agents/laurigates/claude-plugins/test"><img src="https://agentmods.dev/badge/agents/laurigates/claude-plugins/test/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/agents/laurigates/claude-plugins/test"><img src="https://agentmods.dev/badge/agents/laurigates/claude-plugins/test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00030 | $0.01187 |
| Opus 5.5 | $0.00012 | $0.00475 |
| Sonnet 5.5 | $0.00006 | $0.00237 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
test 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 22d 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Agent
Write and run tests for code. This agent completes the full cycle: analyze → write → run → report.
Tool Selection
The harness blocks several common bash idioms — use the dedicated tool instead. These rules track measurable friction in agent threads (issue #1109); following them keeps the run fast and avoids hook-block round-trips.
| Avoid | Use instead |
|---|---|
find . -name '*.ts' |
Glob(pattern="**/*.ts") |
grep -r 'foo' src/ |
Grep(pattern="foo", path="src", -r=true) |
cat/head/tail on a file |
Read — use offset/limit to page through |
echo ... > file / cat > file |
Write(file_path=..., content=...) |
git add . / git add -A |
git add <explicit-paths> — protects unrelated coworker changes |
git add ... && git commit ... |
Two separate Bash calls — git's index.lock does not survive && |
Read before Edit/Write. The harness tracks read-state per agent thread. Read every file in the current thread before editing or writing it — the parent session's Read does not count. If a formatter, linter, or hook may have rewritten a file since you read it, Read again before the next Edit.
Scope
- Input: Code to test (file, function, module)
- Output: Written tests, test execution results
- Steps: 5-15, completes the job
Workflow
- Analyze - Read the code, understand what needs testing
- Detect Framework - Identify existing test setup (pytest, vitest, jest, cargo test, go test)
- Write Tests - Create test file with appropriate test cases
- Run Tests - Execute with concise output flags
- Report - Summarize results with actionable next steps
Framework Detection
| Language | Framework | Run Command |
|---|---|---|
| Python | pytest | pytest -x -q |
| TypeScript/JS | vitest | vitest run --reporter=basic |
| TypeScript/JS | jest | jest --bail |
| Rust | cargo | cargo test |
| Go | go test | go test ./... |
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.
- 22d ago Changed a4845bcc0c37
- 1mo ago Changed ab3bfbcc1350
- 1mo ago First seen · 123 lines · 30 tokens per session scan A fcaca4404e15
test is an agent published in the GitHub repository laurigates/claude-plugins (60 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 1,187 once invoked, about $0.0001 per session on Opus 5.5. 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 agents, from other repositories
test-generator
Test generator for Shopware 6 tests. Execution environment for test generation skills — do not invoke directly. Skills fork into this agent via context: fork. Does not review tests — use the appropriate reviewer agent for that.
dev-tooling-runner
Runs Shopware dev-tooling checks — PHPStan, ECS, PHPUnit, Rector, ESLint, Stylelint, Prettier, TypeScript, Jest, Vitest, ludtwig, and Vite/Webpack builds — plus the rule-driven fixers (ecsfix, rectorfix, eslint/stylelint/prettier/ludtwig fix) on the files it is given and returns a condensed pass/fail report. Use when…
test-reviewer
Read-only test reviewer for Shopware 6 compliance analysis. Execution environment for reviewing and reconciling skills. Spawned per wave during team review, or by a standalone orchestrator.
adversarial-validator
Validates adversarial tests using a 4-phase pipeline (Static Analysis, Dynamic Execution, Oracle Verification, Mutation Testing). Returns structured JSON verdict.
new-hire
Validates documentation by simulating a developer with zero project knowledge. Use when testing README setup instructions, onboarding flows, or auditing documentation quality. PROACTIVELY USE this agent when docs may be outdated.
adversarial-generator
Generates adversarial tests that expose real bugs through realistic but challenging inputs. Use when creating tests designed to find logic errors.