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 stunt-double/stuntdouble-mcp --skill run-qa-suitegit clone --depth 1 https://github.com/stunt-double/stuntdouble-mcpWrote 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/stunt-double/stuntdouble-mcp/run-qa-suite)<a href="https://agentmods.dev/skills/stunt-double/stuntdouble-mcp/run-qa-suite"><img src="https://agentmods.dev/badge/skills/stunt-double/stuntdouble-mcp/run-qa-suite/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/stunt-double/stuntdouble-mcp/run-qa-suite"><img src="https://agentmods.dev/badge/skills/stunt-double/stuntdouble-mcp/run-qa-suite.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.00716 |
| Opus 5 | $0.00014 | $0.00358 |
| Sonnet 5 | $0.00006 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
run-qa-suite 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 10d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run QA suite
When to use
- Before a release to validate all critical user journeys
- After a major refactor to check for regressions
- On a scheduled cadence (weekly, per-sprint) for continuous quality monitoring
- When onboarding a new team member who wants to see current product quality
Instructions
-
Discover the workspace and all validations:
list_workspaces()→ find the target workspacelist_workflows(workspace_id)→ get all journey workflowslist_checklists(workspace_id)→ get all quality checklists
-
Trigger all runs:
run_workflow(workflow_id)→ trigger each workflow (collect all run IDs)run_checklist(checklist_id)→ trigger each checklist (collect all run IDs)- Trigger all runs in parallel for speed
-
Poll all runs to completion:
get_workflow_run(run_id)→ poll each workflow runget_checklist_run(run_id)→ poll each checklist run- Wait until all runs have completed
-
Compile the QA report:
- List every workflow and checklist with pass/fail
- For failures: include step name, actor, and what went wrong
- Compare against previous runs if available:
get_workflow(workflow_id)returnsrecent_runs
-
Check for new feedback generated:
list_feedback(project_id, status: "new")→ see if runs surfaced new issues- Include any new feedback in the report
-
Produce a release-readiness verdict:
- GO — all workflows and checklists pass, no new blockers
- CONDITIONAL — minor issues found but no blockers, document known issues
- NO-GO — blocker-level failures, list what must be fixed
Example report
QA Suite Report — v2.5.0 Release Candidate
Environment: staging.example.com
Date: 2026-03-28
WORKFLOWS (4 total):
[PASS] Signup → First Project ............ 6/6 steps
[PASS] Checkout Flow .................... 5/5 steps
[FAIL] Team Onboarding .................. 4/7 steps (step 5: invite email not received)
[PASS] Account Settings ................. 4/4 steps
CHECKLISTS (3 total):
[PASS] Core Accessibility ............... 10/10 checks
[PASS] Performance Budget ............... 5/5 checks
[FAIL] Content Quality .................. 7/8 checks (placeholder text on billing page)
VERDICT: CONDITIONAL
- 1 workflow failure (team invite email delivery) — non-blocking, known infra issue
- 1 checklist failure (placeholder text) — cosmetic, can ship with known issue
NEW FEEDBACK: 2 items surfaced during this run
- FB-401: Invite flow shows "undefined" in success message
- FB-402: Billing page has "Lorem ipsum" in FAQ section
RECOMMENDATION: Safe to release with documented known issues.
Fix invite email and billing placeholder in next patch.
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.
- 10d ago First seen · 75 lines · 28 tokens per session scan A d67a9323b08b
run-qa-suite is a skill published in the GitHub repository stunt-double/stuntdouble-mcp (1 stars, last pushed 25d ago), licensed MIT. It adds 28 tokens to every session and 716 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-08-31.
Other skills, from other repositories
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
qa/e2e-playwright
A method for writing Playwright end-to-end tests, which automate a browser to verify complete user journeys. It covers setup, reusable page objects, login reuse, API mocking, visual checks, multiple browsers and screen sizes, CI, and debugging.
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.