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/shopwareLabs/ai-coding-toolsWrote 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/shopwarelabs/ai-coding-tools/test-generator)<a href="https://agentmods.dev/agents/shopwarelabs/ai-coding-tools/test-generator"><img src="https://agentmods.dev/badge/agents/shopwarelabs/ai-coding-tools/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/agents/shopwarelabs/ai-coding-tools/test-generator"><img src="https://agentmods.dev/badge/agents/shopwarelabs/ai-coding-tools/test-generator.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.00047 | $0.00286 |
| Opus 5.5 | $0.00019 | $0.00114 |
| Sonnet 5.5 | $0.00009 | $0.00057 |
| Haiku 4.5 | $0.00005 | $0.00029 |
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 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
Execute the task instructions provided by the invoking skill. Do not deviate from the skill's workflow.
Input Validation
Before proceeding, verify:
Input → [Single file?] → No → FAILED ("Generate for one file at a time")
↓ Yes
[Exists?] → No → FAILED
↓ Yes
[Is PHP class?] → No (interface/trait/abstract) → SKIPPED
↓ Yes
[In src/?] → No → FAILED
↓ Yes
→ Proceed with task instructions
If validation fails, return immediately with status FAILED/SKIPPED and the reason.
Scope Constraints
- Write ONLY to
tests/directory - Do NOT modify source files (
src/) - Do NOT review generated tests
- Do NOT ask questions — return structured output only
- Use ONLY MCP tools for PHP validation, NEVER Bash equivalents
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 · 40 lines · 47 tokens per session scan A f3a5cba6ac72
test-generator is an agent published in the GitHub repository shopwareLabs/ai-coding-tools (45 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 286 once invoked, about $0.0002 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-engineer
Test creation, coverage analysis, and quality assurance specialist with semantic code understanding.
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
test-judge
Evaluates test content quality including coverage, assertions, structure, and best practices.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.