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 Kevin-Liu-01/Agent-Machines --skill gstack-qagit clone --depth 1 https://github.com/Kevin-Liu-01/Agent-MachinesWrote 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/kevin-liu-01/agent-machines/gstack-qa)<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/gstack-qa"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/gstack-qa/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/kevin-liu-01/agent-machines/gstack-qa"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/gstack-qa.svg" alt="Reviewed on agentmods" width="80" 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.00061 | $0.01228 |
| Opus 5 | $0.00030 | $0.00614 |
| Sonnet 5 | $0.00012 | $0.00246 |
| Haiku 4.5 | $0.00006 | $0.00123 |
Grade A, and why
gstack-qa 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- qa — 89% identical, 13 lines differ
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.
QA — Test, Find Bugs, Fix, Verify
You are a QA lead testing a real application in a real browser. You find bugs, fix them, generate regression tests, and verify.
Contract
This skill guarantees:
- Real browser testing via agent-browser (Lightpanda default, Chrome for auth)
- Every bug found has a reproduction path with screenshots
- Fixes are atomic (one commit per bug)
- Every fix generates a regression test
- Tests run and pass before the fix is committed
- Commit format:
fix(qa): BUG-NNN — description - Test commit format:
test(qa): regression test for BUG-NNN
Phases
Phase 1: Discover the App
agent-browser snapshot <url>
Understand the app:
- What is this? (Marketing site, dashboard, SaaS app, docs site)
- What are the key user flows?
- What's the tech stack? (Check page source, framework indicators)
- Is auth required? (If redirected to login, ask Kevin for credentials or use
--engine chrome --profilefor existing session)
Phase 2: Test Key Flows
Walk through 3-5 key user flows. For each:
- Navigate to the starting point
- Screenshot the initial state
- Interact — click buttons, fill forms, navigate
- Observe — check for:
- Console errors (
agent-browser console --errors) - Visual glitches (overlapping elements, broken layouts)
- Functional failures (buttons that don't work, forms that don't submit)
- Loading states (missing spinners, infinite loading)
- Error handling (what happens when things go wrong?)
- Responsive behavior (test at 375px, 768px, 1440px)
- Console errors (
- Screenshot the result of each interaction
Phase 3: Bug Report
For each bug found:
BUG-NNN: {title}
=================
Severity: CRITICAL / HIGH / MEDIUM / LOW
Flow: {which user flow}
Steps to reproduce:
1. Navigate to {url}
2. Click {element}
3. Observe {behavior}
Expected: {what should happen}
Actual: {what actually happens}
Screenshot: {path}
Console errors: {if any}
Phase 4: Fix Loop
For each fixable bug, in severity order:
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.
- 7d ago First seen · 154 lines · 61 tokens per session scan A 2d275804b6bc
gstack-qa is a skill published in the GitHub repository Kevin-Liu-01/Agent-Machines (27 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 1,228 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-03.
Other skills, from other repositories
dogfood
This skill guides you through systematic exploratory QA testing of web applications using the browser toolset. You will navigate the application, interact with elements, capture evidence of issues, and produce a structured bug report.
tabnexus-mcp-evals
Generate, validate, and run isolated Codex-to-TabNexus MCP evaluations with a curated 600-query dataset, executable gold tool labels, safety checks, and best-of-three stability scoring. Use when testing TabNexus MCP tool coverage, Agent behavior, regression quality, destructive-action safety, prompt changes, or a…
blazemeter-recorders
Comprehensive guide for BlazeMeter Recorders, including Chrome Extension and Proxy Recorder. Use when working with recorders for (1) Recording tests with Chrome Extension, (2) Creating and using Proxy Recorder, (3) Configuring browsers and devices for proxy recording, (4) Setting port ranges for proxy recorder, or any…
qa-runner
Use when asked to "run QA", "qa check", "test checklist", or execute QA checklists against a running app via browser automation. Requires the browser-bridge MCP server and Chrome extension.
pursr
Use Pursr for browser screenshots, scripted visual operation, visual regression, accessibility audits, DOM inspection, and MCP-driven browser sessions. Use when a user asks an agent to inspect a site, operate an existing browser session, fill or draft UI content, record a tutorial, compare visuals, debug layout, or…
playwright-browser-automation
Run automated headless browser testing, scrape dynamic SPAs, capture high-resolution full-page screenshots, and perform visual regression testing with Playwright.