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 summarybotng/summarybot-ng --skill holistic-testing-pactgit clone --depth 1 https://github.com/summarybotng/summarybot-ngWrote 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/summarybotng/summarybot-ng/holistic-testing-pact)<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/holistic-testing-pact"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/holistic-testing-pact/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/summarybotng/summarybot-ng/holistic-testing-pact"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/holistic-testing-pact.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.00061 | $0.01413 |
| Opus 5 | $0.00030 | $0.00707 |
| Sonnet 5 | $0.00012 | $0.00283 |
| Haiku 4.5 | $0.00006 | $0.00141 |
Grade A, and why
holistic-testing-pact 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 5d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Holistic Testing Model with PACT Principles
<default_to_action> When designing test strategies or building quality into teams:
- APPLY PACT principles: Proactive (test before bugs), Autonomous (teams own quality), Collaborative (whole-team responsibility), Targeted (risk-focused)
- IDENTIFY quadrant focus: Technology-facing (unit, integration, performance) or Business-facing (acceptance, exploratory, usability)
- SELECT agents based on PACT dimension and testing quadrant
- IMPLEMENT feedback loops that catch issues in minutes, not days
- MEASURE outcomes (bug escape rate, release confidence) not activities (test count)
Quick PACT Application:
- Proactive → Design testability into architecture, risk analysis during refinement
- Autonomous → Devs run tests locally, CI pipeline with no manual gates
- Collaborative → Three Amigos, QE pairs with dev, shared test ownership
- Targeted → Risk-based planning, focus on critical flows, kill valueless tests
Critical Success Factors:
- Quality is a whole-team responsibility, not a QA phase
- QA as enablers (build infrastructure, coach), not gatekeepers
- Fast feedback during development, not after </default_to_action>
Quick Reference Card
When to Use
- Designing comprehensive test strategies
- Building quality culture in teams
- Choosing testing approach for new projects
- Evolving from sequential QA to concurrent quality
PACT Principles
| Principle | Focus | Anti-Pattern |
|---|---|---|
| Proactive | Test before code, design testability | Waiting for bugs to find you |
| Autonomous | Teams deploy when ready | QA as manual gatekeepers |
| Collaborative | Whole-team quality thinking | QA works in isolation |
| Targeted | Risk-based, high-value tests | Exhaustive checkbox testing |
Holistic Testing Quadrants
| Quadrant | Purpose | Examples |
|---|---|---|
| Tech + Support | Fast feedback | Unit, component, integration tests |
| Tech + Critique | Find limits | Performance, security, chaos |
| Business + Support | Shared understanding | BDD, acceptance tests |
| Business + Critique | Discover unknowns | Exploratory, usability, A/B |
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.
- 5d ago First seen · 175 lines · 61 tokens per session scan A f7683aabb826
holistic-testing-pact is a skill published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 1,413 once invoked, about $0.0003 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
quality-gate
Orchestrates the QUALITY pipeline stage for egregore work items, running code review, unbloat, and test updates. Use when running quality checks before a PR.
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.
testing-integration
Integration and contract testing patterns — API endpoint tests, component integration, database testing, Pact contract verification, property-based testing, and Zod schema validation. Use when testing API boundaries, verifying contracts, or validating cross-service integration.
golden-dataset
Golden dataset lifecycle patterns for curation, versioning, quality validation, and CI integration. Use when building evaluation datasets, managing dataset versions, validating quality scores, or integrating golden tests into pipelines.
Contract Test Generator
Generate consumer-driven contract tests using Pact framework to verify API provider-consumer compatibility and prevent integration breaking changes.
Contract Testing with Pact
Consumer-driven contract testing skill using Pact, covering consumer tests, provider verification, Pact Broker integration, and CI/CD workflows.