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-executorgit 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-executor)<a href="https://agentmods.dev/skills/matteocervelli/llms/test-executor"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/test-executor/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-executor"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/test-executor.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.00032 | $0.03182 |
| Opus 5 | $0.00016 | $0.01591 |
| Sonnet 5 | $0.00006 | $0.00636 |
| Haiku 4.5 | $0.00003 | $0.00318 |
Grade A, and why
test-executor 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 — 640 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Executor Skill
Purpose
This skill provides systematic test execution capabilities across different test types (unit, integration, e2e) with proper configuration, parallel execution, test filtering, and comprehensive reporting.
When to Use
- Running unit tests for a module or feature
- Executing integration tests with external dependencies
- Running full test suite before commit/PR
- Debugging failing tests with verbose output
- Checking test execution time and performance
- Running tests in different environments (dev, CI/CD)
Test Execution Workflow
1. Test Discovery and Planning
Identify Test Scope:
# Discover all test files
pytest --collect-only
# Count tests by directory
pytest --collect-only tests/unit/
pytest --collect-only tests/integration/
pytest --collect-only tests/e2e/
# Show test structure
pytest --collect-only -q
Analyze Test Organization:
# List all test files
find tests/ -name "test_*.py" -o -name "*_test.py"
# Count tests by type
ls tests/unit/test_*.py | wc -l
ls tests/integration/test_*.py | wc -l
# Check for test markers
grep -r "@pytest.mark" tests/
Deliverable: Test inventory and execution plan
2. Unit Test Execution
Run All Unit Tests:
# Basic execution
pytest tests/unit/
# Verbose output with test names
pytest tests/unit/ -v
# Extra verbose with test details
pytest tests/unit/ -vv
# Show print statements
pytest tests/unit/ -s
# Fail fast (stop on first failure)
pytest tests/unit/ -x
# Run last failed tests only
pytest tests/unit/ --lf
Run Specific Tests:
# Run specific test file
pytest tests/unit/test_feature.py
# Run specific test function
pytest tests/unit/test_feature.py::test_function_name
# Run specific test class
pytest tests/unit/test_feature.py::TestClassName
# Run specific test method
pytest tests/unit/test_feature.py::TestClassName::test_method_name
# Run tests matching pattern
pytest tests/unit/ -k "test_create"
pytest tests/unit/ -k "test_create or test_update"
pytest tests/unit/ -k "not slow"
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 · 640 lines · 32 tokens per session scan A 84bf0e892b96
test-executor is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 3,182 once invoked, about $0.0002 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'…