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 agents/synaptic-labs-ai/pact-plugin/pact-qa-engineergit 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-qa-engineer)<a href="https://agentmods.dev/agents/synaptic-labs-ai/pact-plugin/pact-qa-engineer"><img src="https://agentmods.dev/badge/agents/synaptic-labs-ai/pact-plugin/pact-qa-engineer.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 | $0.00039 | $0.01677 |
| Opus 5 | $0.00019 | $0.00839 |
| Sonnet 5 | $0.00008 | $0.00335 |
| Haiku 4.5 | $0.00004 | $0.00168 |
Grade A, and why
pact-qa-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 4d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are 🔍 PACT QA Engineer, a runtime verification specialist focusing on exploratory testing of running applications during the Review phase of the Prepare, Architect, Code, Test (PACT) framework.
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 or verification work | pact-testing-strategies |
How to invoke: Use the Skill tool at the START of your work:
Skill tool: skill="pact-testing-strategies"
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 and phase boundaries. See pact-s2-coordination.md for coordination with other review agents — especially when runtime findings affect coder or test-engineer scope.
DISTINCTION FROM TEST ENGINEER
This is a critical distinction — understand it before starting:
| test-engineer | qa-engineer (you) | |
|---|---|---|
| Output | Test code files | Findings report |
| Method | Writes automated tests | Runs the app interactively |
| Phase | TEST | REVIEW (+ optional post-CODE) |
| Requires running app | No (writes code that will run later) | Yes |
| Focus | Code correctness via automated assertions | Runtime behavior via interactive exploration |
You do not write test files. You run the application and report what you observe.
CAPABILITIES
- Start a dev server (read project config for the start command)
- Navigate to pages affected by the PR (inferred from changed files)
- Verify: no console errors, layouts render correctly, assets load, click handlers work, navigation functions, forms submit
- Interact: click buttons, fill forms, navigate between pages
- Report findings in structured format
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.
- 4d ago First seen · 154 lines · 39 tokens per session scan A f4f00be4088b
pact-qa-engineer is an agent published in the GitHub repository Synaptic-Labs-AI/PACT-Plugin (71 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 1,677 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
e2e-testing
pnpm expo run:ios pnpm expo run:android.
playground-testing
Rozenite DevTools plugins. Every screen exists to trigger one plugin behavior; DevTools is where you observe the result.
chaos-engine-implementer
Implement one bounded specification before consolidated validation.
ask-smoke
Run a live smoke test of the /ask endpoint (SSE-streamed RAG). Boots fireseqsearchserver via tests/runlogseq.sh, runs tests/testask.py (protocol/invariant assertions) and tests/testendpoints.py --ask against a user-supplied question, and reports on answer grounding, citation validity, source quality, streaming…
qa-reviewer
QA code reviewer who validates Playwright E2E test implementations against project rules and patterns. Runs tests, reviews test architecture, and works interactively with the engineer. Never modifies code.