Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mehdiozdemir/awesome-agent-skillsnpx agentmods add skills/mehdiozdemir/awesome-agent-skills/test-generatorWrote 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/skills/mehdiozdemir/awesome-agent-skills/test-generator)<a href="https://agentmods.dev/skills/mehdiozdemir/awesome-agent-skills/test-generator"><img src="https://agentmods.dev/badge/skills/mehdiozdemir/awesome-agent-skills/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/skills/mehdiozdemir/awesome-agent-skills/test-generator"><img src="https://agentmods.dev/badge/skills/mehdiozdemir/awesome-agent-skills/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.00051 | $0.08570 |
| Opus 5 | $0.00026 | $0.04285 |
| Sonnet 5 | $0.00010 | $0.01714 |
| Haiku 4.5 | $0.00005 | $0.00857 |
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 11d 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 — 1,293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Generator Skill
This skill creates thorough, maintainable test suites following testing best practices. Use this whenever you need to generate unit tests, integration tests, or end-to-end tests for any codebase.
Testing Principles
1. Test Structure (AAA Pattern)
Arrange → Act → Assert
- Arrange: Set up test data and preconditions
- Act: Execute the code under test
- Assert: Verify the expected outcome
2. F.I.R.S.T. Principles
- Fast: Tests should run quickly
- Independent: No dependencies between tests
- Repeatable: Same result every time
- Self-validating: Clear pass/fail outcome
- Timely: Written alongside production code
3. Test Coverage Goals
- Happy path (expected behavior)
- Edge cases (boundary conditions)
- Error cases (exception handling)
- Invalid inputs (validation)
- Performance (when relevant)
Test Types
Unit Tests
- Test single functions or methods in isolation
- Mock external dependencies
- Fast execution (milliseconds)
- High coverage target (80%+)
Integration Tests
- Test component interactions
- Use real dependencies (database, APIs)
- Medium execution time
- Focus on critical paths
End-to-End Tests
- Test complete user flows
- Run against production-like environment
- Slower execution
- Cover business-critical scenarios
Test Generation Process
Step 1: Analyze the Code
- Identify the function/class to test
- Understand input parameters and types
- Determine expected outputs
- Identify dependencies to mock
- Note edge cases and error conditions
Step 2: Plan Test Cases
Systematically cover:
Input Categories:
- Valid inputs (normal operation)
- Boundary values (min, max, zero)
- Invalid inputs (null, undefined, wrong type)
- Empty inputs (empty string, empty array)
- Special values (infinity, NaN, special chars)
State Categories:
- Initial state
- Populated state
- Error state
- Edge state
Step 3: Generate Tests
Create tests following language conventions:
- Descriptive test names
- Clear arrangement
- Single assertion per test (when possible)
- Proper cleanup
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.
- 11d ago First seen · 1,293 lines · 51 tokens per session scan A 5ef23fd5e842
test-generator is a skill published in the GitHub repository mehdiozdemir/awesome-agent-skills (2 stars, last pushed 7mo ago), licensed MIT. It adds 51 tokens to every session and 8,570 once invoked, about $0.0003 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 skills, from other repositories
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
prd-auto-test-loop
A testing workflow driven by a product requirements document (PRD), which describes what a software version should do. It turns acceptance criteria into unit, integration, and end-to-end tests, then records the plan and results.
test-automation-expert
Comprehensive test automation specialist covering unit, integration, and E2E testing strategies. Expert in Jest, Vitest, Playwright, Cypress, pytest, and modern testing frameworks. Guides test pyramid design, coverage optimization, flaky test detection, and CI/CD integration. Activate on 'test strategy', 'unit tests'…