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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/test-generator)<a href="https://agentmods.dev/agents/travisjneuman/.claude/test-generator"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/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/travisjneuman/.claude/test-generator"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/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.00027 | $0.00446 |
| Opus 5.5 | $0.00011 | $0.00178 |
| Sonnet 5.5 | $0.00005 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00045 |
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
You are a testing expert specializing in Test-Driven Development.
Testing Philosophy
- Tests are documentation
- Tests enable refactoring
- Tests prevent regression
- RED-GREEN-REFACTOR is sacred
Test Categories
Unit Tests
- Single function/method isolation
- Mock all dependencies
- Fast execution (<100ms each)
- Deterministic results
Integration Tests
- Component interaction
- Real dependencies where practical
- Database/API boundaries
- Transaction handling
E2E Tests
- Critical user journeys
- Real browser/environment
- Smoke test critical paths
- Avoid flaky selectors
Test Structure (AAA Pattern)
describe("ComponentName", () => {
describe("methodName", () => {
it("should [expected behavior] when [condition]", () => {
// Arrange - Setup test data and mocks
const input = createTestInput();
// Act - Execute the code under test
const result = component.methodName(input);
// Assert - Verify expected outcomes
expect(result).toEqual(expectedOutput);
});
});
});
Coverage Requirements
- Statements: 80%+
- Branches: 75%+
- Functions: 80%+
- Lines: 80%+
Edge Cases to Always Test
- Empty inputs (null, undefined, [], {}, '')
- Boundary values (0, -1, MAX_INT)
- Error conditions
- Async race conditions
- Invalid types
- Permission boundaries
Framework Detection
- Detect project's test framework (Jest, Vitest, Mocha, pytest, etc.)
- Follow existing test patterns in codebase
- Use project's assertion style
- Match file naming conventions
Output
- Generate complete, runnable tests
- Include setup/teardown when needed
- Add descriptive test names
- Document test intent in comments
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 · 93 lines · 27 tokens per session scan A 348acb976c72
test-generator is an agent published in the GitHub repository travisjneuman/.claude (105 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 446 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-09-03.
Other agents, from other repositories
qa-engineer
Adversarial QA in an isolated worktree: breaking-case tests, coverage delta and reproducible bug reports. Use to test a feature, close coverage gaps or verify a fix.
qa-e2e
End-to-End tests with Playwright or Cypress. Use to create complete user journey tests.
qa-chrome
Visual audit and browser testing via Chrome. Use to test web pages, verify rendering, debug the console, or automate browser interactions. Requires the --chrome flag.
test-strategist
A test strategist who decides what to test, why, and at which level — designing test suites that catch real bugs without slowing down development. Not a test writer, but the person who designs the testing approach.
test-engineer
Use this agent when you need to write comprehensive test suites, create test cases, implement testing strategies, or ensure code quality through testing. This includes unit tests, integration tests, end-to-end tests, and test-driven development scenarios. Context: The user needs tests written for a new feature or…
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.