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 skills/paruff/ufawkesai/test-executionnpx skills add paruff/uFawkesAI --skill test-executiongit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/test-execution)<a href="https://agentmods.dev/skills/paruff/ufawkesai/test-execution"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/test-execution.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.1 | $0.00028 | $0.00730 |
| Opus 5 | $0.00014 | $0.00365 |
| Sonnet 5 | $0.00006 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
test-execution 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 2d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Test Execution
Load trigger:
"load test-execution skill"> DORA: Cap 5 (Small Batches / Shift Left on Quality) Token cost: Low
Purpose
Execute all relevant tests and quality gates to validate build output.
Responsibilities
- Execute unit, integration, and E2E tests
- Collect test results and failure details
- Measure code coverage
- Validate test viability
- Run quality gates (lint, typecheck)
Sub-Skills
| Skill | Purpose |
|---|---|
test-execution/unit-test-execution |
Run unit tests and measure coverage |
test-execution/integration-test-execution |
Run integration tests |
test-execution/e2e-test-execution |
Run end-to-end tests |
test-execution/test-coverage-validation |
Validate coverage thresholds |
test-execution/pipeline-test-stage-validation |
Validate CI test stages |
test-execution/runtime-simulation-validation |
Simulate runtime environment |
test-execution/performance-smoke-testing |
Basic performance validation |
Dependencies
| Skill | Relationship |
|---|---|
build |
Consumes source code and test files |
test |
Validates tests written by test agent |
Inputs
- Source code (from build)
- Test files (from test agent)
- Test configuration
Outputs
test-results.jsontest-report.mdcoverage-report.json
Execution Rules
Pre-Run
- Test framework installed and configured
- Test files discovered and counted
- Dependencies available
Execution
- All tests executed
- No tests skipped without justification
- Test output captured
- Exit code checked (non-zero = failure)
Post-Run
- Pass/fail counts recorded
- Failure details captured
- Coverage data collected
- Flaky tests flagged
What ships with it
8 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.
- e2e-test-execution/SKILL.md 2.7 KB
- integration-test-execution/SKILL.md 2.5 KB
- live-system-verification/SKILL.md 4.5 KB
- performance-smoke-testing/SKILL.md 3.5 KB
- pipeline-test-stage-validation/SKILL.md 3.2 KB
- runtime-simulation-validation/SKILL.md 2.9 KB
- test-coverage-validation/SKILL.md 2.6 KB
- unit-test-execution/SKILL.md 2.1 KB
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.
- 2d ago First seen · 117 lines · 28 tokens per session scan A 6962300c1c61
test-execution is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 13d ago), licensed MIT. It adds 28 tokens to every session and 730 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
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.
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
qa/test-strategy
测试策略和测试金字塔原则，定义单元测试、集成测试、E2E测试的分布和覆盖要求.
Codeception Testing
Expert-level Codeception testing skill for PHP applications. Covers acceptance, functional, and unit testing with the Actor pattern, BDD-style syntax, Page Objects, API testing, and database helpers.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
claude-code-qa
The complete QA skill for Claude Code — turn Claude into an expert QA engineer that picks the right test type, writes reliable Playwright, Cypress, and pytest tests, eliminates flaky tests, enforces coverage, and wires up CI. Claude Code QA testing done right.