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.
npx agentmods add commands/thelobbi/claude/generate-testsgit clone --depth 1 https://github.com/TheLobbi/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/commands/thelobbi/claude/generate-tests)<a href="https://agentmods.dev/commands/thelobbi/claude/generate-tests"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/generate-tests.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00314 |
| Opus 5 | $0.00000 | $0.00157 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
generate-tests 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 4d 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
Test Suite Generation
Generate comprehensive test suites for the codebase with focus on coverage and quality:
Test Strategy
- Identify untested or under-tested code paths
- Generate unit tests for individual functions/methods
- Create integration tests for component interactions
- Add end-to-end tests for critical user flows
- Include edge cases and error scenarios
Test Types to Generate
-
Unit Tests
- Pure function testing
- Component testing (React, Vue, etc.)
- Service/utility testing
- Mock external dependencies
-
Integration Tests
- API endpoint testing
- Database interaction testing
- Service integration testing
- Third-party integration testing
-
Edge Cases
- Boundary conditions
- Null/undefined handling
- Empty arrays/objects
- Invalid input handling
- Error scenarios
-
Performance Tests (where applicable)
- Load testing
- Stress testing
- Benchmark tests
Test Framework Guidelines
- Use existing test framework (Jest, Mocha, Pytest, etc.)
- Follow AAA pattern (Arrange, Act, Assert)
- Use descriptive test names
- Include setup and teardown
- Mock external dependencies appropriately
- Aim for high code coverage (>80%)
Output
Generate test files with:
- Clear test descriptions
- Comprehensive assertions
- Proper mocking/stubbing
- Comments explaining complex test logic
- Coverage for happy path and error cases
Report current test coverage and areas needing attention.
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.
- 4d ago First seen · 54 lines · 0 tokens per session scan A 74846ee2ea70
generate-tests is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 314 tokens. 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 commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
gsd:add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
testing
Comprehensive testing through distributed execution.
verify
You are invoking the verify skill - comprehensive verification following Boris Cherny's pattern.
test
Escrever e rodar testes (skill 05 — QA Engineer).
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.