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 integration-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/integration-test-execution)<a href="https://agentmods.dev/skills/paruff/ufawkesai/integration-test-execution"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/integration-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/integration-test-execution"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/integration-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.00023 | $0.00583 |
| Opus 5 | $0.00012 | $0.00292 |
| Sonnet 5 | $0.00005 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
integration-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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Integration Test Execution
Load trigger:
"load integration-test-execution skill"> DORA: Cap 5 (Small Batches / Shift Left on Quality) Token cost: Low
Purpose
Validate interactions between components.
Responsibilities
- Execute integration test suite
- Validate component interactions
- Validate data flow correctness
- Detect integration failures
Inputs
- Build output
- Integration test files
- Test configuration
Outputs
integration-test-results.jsonintegration-test-report.md
Execution Rules
Pre-Run
- Required services/dependencies available (or mocked)
- Test database/datastore configured
- Network dependencies accessible or simulated
- Environment variables set
Execution
- All integration tests executed
- Service interactions validated
- Data flow validated
- Timeout and retry behavior validated
Post-Run
- Pass/fail counts recorded
- Failure details captured
- Integration points documented
- External dependency issues flagged
Integration Points
Common Integration Boundaries
- API ↔ Database
- API ↔ External Service (payment, email, etc.)
- Service ↔ Service (internal RPC/messaging)
- Frontend ↔ Backend (API calls)
- CLI ↔ Filesystem
Validation Rules
- Database queries return expected shapes
- External service responses handled correctly
- Error responses propagated correctly
- Timeouts handled gracefully
- Retries follow exponential backoff
Tools
| Language | Runner | Notes |
|---|---|---|
| TypeScript | Jest / Vitest | --integration flag or separate config |
| Python | pytest | Markers: @pytest.mark.integration |
| Go | go test |
Build tags: //go:build integration |
Output Format
{
"skill": "integration-test-execution",
"status": "pass | fail",
"total": 8,
"passed": 8,
"failed": 0,
"integration_points_tested": ["API ↔ Database", "API ↔ External Service"],
"failures": []
}
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 · 106 lines · 23 tokens per session scan A de5c594f2c95
integration-test-execution is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 19d ago), licensed MIT. It adds 23 tokens to every session and 583 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
api-tester
Test and document API endpoints - validate responses, check status, generate examples.
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
Contract Test Generator
Generate consumer-driven contract tests using Pact framework to verify API provider-consumer compatibility and prevent integration breaking changes.
api-testing-rest
Comprehensive RESTful API testing patterns covering HTTP methods, status codes, request/response validation, authentication, error handling, and contract testing.
Contract Testing with Pact
Consumer-driven contract testing skill using Pact, covering consumer tests, provider verification, Pact Broker integration, and CI/CD workflows.
playwright-api
API testing skill using Playwright's built-in APIRequestContext for RESTful service validation, authentication flows, and API contract verification.