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 Mathews-Tom/armory --skill qa-systematicgit clone --depth 1 https://github.com/Mathews-Tom/armoryWrote 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/mathews-tom/armory/qa-systematic)<a href="https://agentmods.dev/skills/mathews-tom/armory/qa-systematic"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/qa-systematic.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00062 | $0.01318 |
| Opus 5 | $0.00031 | $0.00659 |
| Sonnet 5 | $0.00012 | $0.00264 |
| Haiku 4.5 | $0.00006 | $0.00132 |
Grade A, and why
qa-systematic 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 2d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systematic QA Testing
Modes
Full (default)
Systematic page-by-page testing, 8-category health score, full issue documentation.
Quick
30-second smoke test of critical paths only: login, main nav, primary action.
Regression
Diff current state against saved baseline, report new/resolved issues.
Browser Automation Detection
Detect available automation in priority order:
- Playwright MCP server — check if Playwright tools are available in the current tool list
agent-browserskill — check if the agent-browser skill is loaded- Direct CLI tools — check for
playwright,puppeteer, orcypressbinaries on PATH - Manual fallback — instruct the user to navigate and report observations
Use the highest-priority method available. State which method is in use at the start of the report.
Workflow
Phase 1: Initialize
- Detect mode from user prompt. Default to full if unspecified.
- Detect application URL:
- Check
references/project-detection.mdfor framework port conventions (e.g., Next.js → 3000, Vite → 5173, Django → 8000). - If not detectable, ask the user.
- Check
- Detect available browser automation method (priority list above).
- If regression mode: load previous baseline from
.qa-reports/.
Phase 2: Authenticate (if needed)
- Navigate to root URL and check if a login wall is present.
- If credentials were provided: authenticate and store session.
- If not: ask the user for test credentials, or skip auth-gated pages and note the gap in the report.
Phase 3: Orient
- Navigate to root URL.
- Map the primary navigation structure — collect all top-level nav links.
- Classify each page: static, form, list, detail, dashboard.
- Build a test plan ordered by page category (forms and dashboards first — highest defect density).
Phase 4: Explore (Full mode)
For each page, run the per-page checklist below. In quick mode, run only the items marked with (Q).
Visual Scan
- (Q) Layout renders correctly — no overlap, no overflow
- Images load — no broken
<img>tags - Typography consistent — no visible font fallbacks
- Responsive: check at desktop (1280px) and mobile (375px) widths
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 168 lines · 62 tokens per session scan A cc981ac659a5
qa-systematic is a skill published in the GitHub repository Mathews-Tom/armory (316 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 1,318 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-05.
Other skills, from other repositories
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…
playwright-skill
Complete browser automation with Playwright. Auto-detects dev servers, writes reusable test scripts, and supports screenshots, responsive checks, UX validation, login flows, link checks, and arbitrary browser automation. Use when the user wants to test a website, automate browser interactions, validate web…
actionbook-web-test
Run browser-based web tests against websites using Actionbook CLI. Activate when the user wants to test a website workflow, run smoke tests, verify a user flow, check if a web application works, run regression tests, or validate browser-based interactions. Supports test definition, execution, assertion, reporting, and…
web-test
A browser-automation tool for testing the 1C:Enterprise web client. It uses Playwright to navigate sections, fill forms, read tables and reports, and perform user actions in a browser.
playwright-visual-testing
Add, repair, or review Playwright visual regression tests for browser-facing .NET apps, including screenshot baselines, Pixelmatch thresholds, deterministic rendering, and GitHub Actions artifacts. USE FOR: toHaveScreenshot, page.screenshot visual checks, Pixelmatch/pngjs comparison scripts, visual baseline updates…
e2e-testing
Playwright and Cypress patterns, selectors, assertions, API mocking, visual testing, and CI/CD.