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 paruff/uFawkesAI --skill unit-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/unit-test-execution)<a href="https://agentmods.dev/skills/paruff/ufawkesai/unit-test-execution"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/unit-test-execution/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/paruff/ufawkesai/unit-test-execution"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/unit-test-execution.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.00028 | $0.00560 |
| Opus 5 | $0.00014 | $0.00280 |
| Sonnet 5 | $0.00006 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
unit-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 8d 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
Skill: Unit Test Execution
Load trigger:
"load unit-test-execution skill"> DORA: Cap 5 (Small Batches / Shift Left on Quality) Token cost: Low
Purpose
Run unit tests and validate correctness of individual components.
Responsibilities
- Execute unit test suite
- Collect test results and failure details
- Collect coverage data
- Detect flaky or skipped tests
Inputs
- Source code
- Unit test files
- Test configuration (
jest.config.ts,pytest.ini, etc.)
Outputs
unit-test-results.jsonunit-test-report.md
Execution Rules
Pre-Run
- Test framework installed and configured
- Test files discovered and counted
- Dependencies available (no missing modules)
Execution
- All unit tests executed
- No tests skipped without justification
- Test output captured (stdout, stderr)
- Exit code checked (non-zero = failure)
Post-Run
- Pass/fail counts recorded
- Failure details captured (test name, assertion, file:line)
- Coverage data collected (line, branch, function)
- Flaky tests flagged (if detectable)
Tools
| Language | Runner | Coverage |
|---|---|---|
| TypeScript | Jest / Vitest | --coverage |
| Python | pytest | pytest-cov |
| Go | go test |
-coverprofile |
| Rust | cargo test |
cargo-tarpaulin |
Output Format
{
"skill": "unit-test-execution",
"status": "pass | fail",
"total": 44,
"passed": 42,
"failed": 0,
"skipped": 2,
"coverage": {
"line": 87.5,
"branch": 79.2,
"function": 92.1
},
"failures": [],
"skipped_tests": ["test name 1"]
}
Success Criteria
- All unit tests pass
- Coverage data collected successfully
- No unexplained skips
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.
- 8d ago First seen · 94 lines · 28 tokens per session scan A ad1e077f7f39
unit-test-execution is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 19d ago), licensed MIT. It adds 28 tokens to every session and 560 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
template-formal
Strongly-typed multiagent ant-robot colony exemplar — ADTs, session-typed protocols, affine-discipline resource handles, storage-as-functor framing, Active-Inference-flavored decision loop, mypy-as-oracle negative controls.
template-test-creation
Create pytest suites under the no-mocks policy — real data, temp files, subprocess, pytest-httpserver. USE WHEN adding tests, raising coverage, testing new src/ module, or user forbids mocks.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
template-code-project
Code-centric optimization research exemplar — gradient descent, convergence analysis, automated figures, dashboard, and publication-quality PDF.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.