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 skills add matteocervelli/llms --skill test-generatorgit clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/test-generator)<a href="https://agentmods.dev/skills/matteocervelli/llms/test-generator"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/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/matteocervelli/llms/test-generator"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/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.00019 | $0.01632 |
| Opus 5 | $0.00010 | $0.00816 |
| Sonnet 5 | $0.00004 | $0.00326 |
| Haiku 4.5 | $0.00002 | $0.00163 |
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 6d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Generator Skill
Purpose
This skill provides comprehensive test scaffolding and templates for quickly setting up unit and integration tests with proper structure, fixtures, and mocking configurations. It guides the creation of well-structured, maintainable tests following best practices.
Activation
On-demand via command: /generate-tests <file-path>
Example:
/generate-tests src/tools/example/core.py
When to Use
- Starting tests for a new module
- Need test structure quickly
- Adding tests to existing code
- Setting up test fixtures and mocks
- Creating integration test scaffolding
- Following pytest or Jest best practices
Resources
testing-templates/unit-test.py
Complete pytest unit test template with:
- Proper import structure
- Fixture definitions (sample data, temp files, mocks)
- Test function templates (Arrange-Act-Assert pattern)
- Test class templates
- Parametrize examples
- Mock/patch configurations
- Common assertion patterns
testing-templates/integration-test.py
Complete integration test template with:
- Service integration patterns
- Database integration examples
- File system test patterns
- End-to-end workflow examples
- Cleanup patterns (tmp_path, fixtures)
- Real dependency testing (not mocked)
Provides
Test File Scaffolding
- Proper file structure and organization
- Naming conventions (
test_*.pyor*_test.py) - Import statements
- Test class/function structure
Fixture Setup
- pytest: Sample fixtures for common use cases
- Jest: Mock implementations and spy configurations
- Reusable test data fixtures
- Setup/teardown patterns
Mock Configurations
- unittest.mock: Mock and patch examples
- pytest-mock: pytest-specific mocking
- Jest: Mock modules and functions
- Spy and stub patterns
Coverage Analysis Helpers
- Test organization for better coverage
- Edge case identification
- Boundary testing patterns
Usage Examples
Example 1: Generate Unit Tests for Module
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 307 lines · 19 tokens per session scan A 2e20cd2eedda
test-generator is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 1,632 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-09-03.
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'…