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/ShaheerKhawaja/ProductionOSWrote 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/commands/shaheerkhawaja/productionos/qa)<a href="https://agentmods.dev/commands/shaheerkhawaja/productionos/qa"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/qa.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.1 | $0.00030 | $0.00592 |
| Opus 5 | $0.00015 | $0.00296 |
| Sonnet 5 | $0.00006 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
qa scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:3000 > /dev/null 2>&1 && echo "Dev server: http://localhost:3000" What it actually says
/qa — Systematic QA Testing
Test the web app systematically. Find bugs. Fix them. Re-test. Score health 0-100.
Step 0: Preamble
Run templates/PREAMBLE.md. Detect dev server URL.
Step 1: Discover
# Detect dev server
curl -s http://localhost:3000 > /dev/null 2>&1 && echo "Dev server: http://localhost:3000"
curl -s http://localhost:8000 > /dev/null 2>&1 && echo "Dev server: http://localhost:8000"
Step 2: Smoke Test
Dispatch browser-controller to navigate key pages:
- Home/landing
- Auth (login/signup)
- Dashboard/main
- Settings
- Any page with forms
Report: loads? errors? missing elements?
Step 3: Deep QA (if mode = full)
Dispatch parallel agents:
browser-controller: Navigate every route, screenshot eachux-auditor: Full WCAG + interaction audit on each pageself-evaluator: Score each page's quality
Step 4: Health Score
Calculate 0-100 score:
- Pages load without error: 20 pts
- No console errors: 15 pts
- Forms work: 15 pts
- Accessibility passes: 15 pts
- Responsive: 15 pts
- Performance (< 3s load): 10 pts
- No broken links: 10 pts
Step 5: Fix Loop (if fix = on)
For each bug found:
- Read the source file causing the issue
- Fix with minimal change
- Re-test to verify fix
- Self-eval the fix quality
Step 6: Report
Write to .productionos/QA-REPORT-{timestamp}.md:
# QA Report
**Health Score:** X/100
**Pages Tested:** N
**Bugs Found:** N
**Bugs Fixed:** N
**Regressions:** N (if regression mode)
Self-Eval
Run templates/SELF-EVAL-PROTOCOL.md on QA thoroughness.
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.
- 6d ago First seen · 78 lines · 30 tokens per session scan A c155dccdb5d9
qa is a command published in the GitHub repository ShaheerKhawaja/ProductionOS (8 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 592 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
lavra-qa
Browser-based QA verification of the running app -- systematic testing from the user's perspective.
test-browser
Run browser tests on pages affected by current PR or branch.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
record
Record the browser while validating a flow, then judge it against a rubric.
qa-run
A command that runs browser tests from a test plan and creates rerunnable checks for important points.