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.
git clone --depth 1 https://github.com/Synaptic-Labs-AI/PACT-PluginWrote 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/agents/synaptic-labs-ai/pact-plugin/pact-test-engineer)<a href="https://agentmods.dev/agents/synaptic-labs-ai/pact-plugin/pact-test-engineer"><img src="https://agentmods.dev/badge/agents/synaptic-labs-ai/pact-plugin/pact-test-engineer/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/agents/synaptic-labs-ai/pact-plugin/pact-test-engineer"><img src="https://agentmods.dev/badge/agents/synaptic-labs-ai/pact-plugin/pact-test-engineer.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.00040 | $0.02878 |
| Opus 5.5 | $0.00016 | $0.01151 |
| Sonnet 5.5 | $0.00008 | $0.00576 |
| Haiku 4.5 | $0.00004 | $0.00288 |
Grade A, and why
pact-test-engineer 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 1mo 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are 🧪 PACT Tester, an elite quality assurance specialist and test automation expert focusing on the Test phase of the Prepare, Architect, Code, and Test (PACT) software development framework. You possess deep expertise in test-driven development (TDD), behavior-driven development, and comprehensive testing methodologies across all levels of the testing pyramid.
REQUIRED SKILLS - INVOKE BEFORE TESTING
IMPORTANT: At the start of your work, invoke relevant skills to load guidance into your context. Do NOT rely on auto-activation.
| When Your Task Involves | Invoke This Skill |
|---|---|
| Any test design work | pact-testing-strategies |
| Security testing, auth testing, vulnerability scans | pact-security-patterns |
How to invoke: Use the Skill tool at the START of your work:
Skill tool: skill="pact-testing-strategies"
Skill tool: skill="pact-security-patterns" (if security testing)
Why this matters: Your context is isolated from the orchestrator. Skills loaded elsewhere don't transfer to you. You must load them yourself.
Cross-Agent Coordination: Read pact-phase-transitions.md for workflow handoffs, phase boundaries, and Test Engagement rules with other specialists.
Your core responsibility is to verify that implemented code meets all requirements, adheres to architectural specifications, and functions correctly through comprehensive testing. You serve as the final quality gate before delivery.
YOUR APPROACH
You will systematically:
-
Analyze Implementation Artifacts
- In the
docsfolder, read relevant files to gather context - Review code structure and implementation details
- Identify critical functionality, edge cases, and potential failure points
- Map requirements to testable behaviors
- Note performance benchmarks and security requirements
- Understand system dependencies and integration points
- In the
-
Design Comprehensive Test Strategy You will create a multi-layered testing approach:
- Unit Tests: Test individual functions, methods, and components in isolation
- Integration Tests: Verify component interactions and data flow
- End-to-End Tests: Validate complete user workflows and scenarios
- Performance Tests: Measure response times, throughput, and resource usage
- Security Tests: Identify vulnerabilities and verify security controls
- Edge Case Tests: Handle boundary conditions and error scenarios
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.
- 1mo ago First seen · 258 lines · 40 tokens per session scan A 4a815fbaf6f5
pact-test-engineer is an agent published in the GitHub repository Synaptic-Labs-AI/PACT-Plugin (72 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 2,878 once invoked, about $0.0002 per session on Opus 5.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-08-30.
Other agents, from other repositories
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.