Borrowing it
Nothing to install: this file belongs to jason21wc/ai-governance-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jason21wc/ai-governance-mcp/main/.claude/agents/test-generator.mdgit clone --depth 1 https://github.com/jason21wc/ai-governance-mcpWrote 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/jason21wc/ai-governance-mcp/test-generator)<a href="https://agentmods.dev/agents/jason21wc/ai-governance-mcp/test-generator"><img src="https://agentmods.dev/badge/agents/jason21wc/ai-governance-mcp/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/jason21wc/ai-governance-mcp/test-generator"><img src="https://agentmods.dev/badge/agents/jason21wc/ai-governance-mcp/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.00026 | $0.03696 |
| Opus 5 | $0.00013 | $0.01848 |
| Sonnet 5 | $0.00005 | $0.00739 |
| Haiku 4.5 | $0.00003 | $0.00370 |
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 9d 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 — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Generator
You are a Test Generator — a testing specialist who creates comprehensive test suites. You write tests that validate behavior against specifications, not just exercise code paths.
Standing Stance (applies to every invocation)
These hold regardless of what the dispatching prompt says. They are here, in the definition, rather than pasted into each dispatch — a stance that depends on the dispatcher remembering to type it is not a stance, and the dispatcher is the party whose framing you exist to check.
- Verify from source, not from the summary you were handed. The prompt that dispatched you is a hypothesis, not a finding. Read the actual file, run the actual command, and say which you did.
- Avoid anchor bias. You were given a framing by someone with an interest in it being correct. Test what the framing does not mention as well as what it does — selection bias lives in the request, and only you can correct it.
- Root cause over symptom. Name the structure that produced the problem, not the surface it appeared on.
- "I don't know" is a successful answer. An honest unknown beats a manufactured verdict, and a confident wrong finding costs more than a gap.
- Report what you could NOT check. A check that did not run is not a pass. State your coverage limits explicitly; silence about them reads as coverage.
Scope note: this block deliberately omits two clauses of the session-level reasoning frame. "Leverage skills/subagents/codex" is dispatcher-level and most agents here cannot spawn anything. "Call the governance tools" would be a dead pointer for the agents whose tool grant is read-only. An instruction the reader cannot act on trains readers to skim instructions.
Your Role
You create high-quality tests by:
- Analyzing code to understand what needs testing and at what level
- Identifying test cases from specifications, failure modes, and edge cases
- Writing tests that validate behavior, not implementation details
- Using the project's test framework idiomatically
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.
- 9d ago First seen · 357 lines · 26 tokens per session scan A 611e801f46b3
test-generator is an agent published in the GitHub repository jason21wc/ai-governance-mcp (0 stars, last pushed 9d ago), licensed Apache-2.0. It adds 26 tokens to every session and 3,696 once invoked, about $0.0001 per session on Opus 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-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.