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 skills/garagon/nanostack/qanpx skills add garagon/nanostack --skill qagit clone --depth 1 https://github.com/garagon/nanostackWrote 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/garagon/nanostack/qa)<a href="https://agentmods.dev/skills/garagon/nanostack/qa"><img src="https://agentmods.dev/badge/skills/garagon/nanostack/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 | $0.00054 | $0.03155 |
| Opus 5 | $0.00027 | $0.01577 |
| Sonnet 5 | $0.00011 | $0.00631 |
| Haiku 4.5 | $0.00005 | $0.00315 |
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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| **API QA** | Backend endpoints, services | curl/httpie-based request testing | How it starts
The opening of the file, as written. The whole thing — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/qa — Quality Assurance & Debugging
You test like a real user and fix like an engineer. Click everything, fill every form, check every state. When you find a bug, you own it: fix it with an atomic commit, re-verify, and move on. If a fix touches more than it should, stop and report instead.
Telemetry preamble
Defensive telemetry init. No-op if telemetry is disabled via NANOSTACK_NO_TELEMETRY=1, ~/.nanostack/.telemetry-disabled, or if the helpers are removed.
_P="$HOME/.claude/skills/nanostack/bin/lib/skill-preamble.sh"
[ -f "$_P" ] && . "$_P" qa
unset _P
Intensity Mode
If the user specifies a mode flag, use it. Otherwise, check bin/init-config.sh for preferences.default_intensity.
| Mode | Flag | Scope | Bug fix limit |
|---|---|---|---|
| Quick | --quick |
Happy path only, screenshots on failure only | Max 3 fixes |
| Standard | (default) | Happy path + error states + empty states | Max 10 fixes |
| Thorough | --thorough |
Happy + error + edge + load + regression tests | Max 20 fixes |
| Report only | --report-only |
Same scope as standard, but NO fixes | 0 — findings only |
--report-only can combine with any intensity: /qa --thorough --report-only scans everything but touches nothing. Use when you want a bug inventory without code changes.
WTF-Likelihood Heuristic
Track regression probability: +15% per revert, +5% per >3-file fix, +20% if touching unrelated files. Stop at 20%. Hard cap: quick=3 fixes, standard=10, thorough=20.
Mode Selection
Determine the testing mode from context:
| Mode | When | Approach |
|---|---|---|
| Browser QA | Web application, UI changes | Playwright-based browser testing |
| Native QA | macOS app, iOS Simulator, Electron, GUI-only tools | Computer use (click, type, screenshot) |
| API QA | Backend endpoints, services | curl/httpie-based request testing |
| CLI QA | Command-line tools | Direct execution with assertions |
| Debug | Known bug, error report, failing test | Root-cause investigation |
What ships with it
2 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.
- 4d ago First seen · 290 lines · 54 tokens per session scan A 0dffd3e55baf
qa is a skill published in the GitHub repository garagon/nanostack (204 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 3,155 once invoked, about $0.0003 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-30.
Other skills, from other repositories
mailagent
Temporary inboxes for agent signup QA — create disposable addresses, wait for verification email, extract OTP or magic links. Use when automating signup, login, or email verification without parsing HTML manually.
write-test-plan
Generate a QA/UAT test plan from product specifications and task definitions, covering acceptance testing, integration flows, and exploratory testing. Unit tests are out of scope (handled by write-unit-tests skill).
e2e-check
Run E2E tests or interactive browser verification. Triggers on: 'run e2e', 'e2e test', 'browser test', 'check in browser', 'verify UI', 'interactive test'.
browser-testing
Tests a real web user flow with a browser by asserting semantic behavior, network and loading states, keyboard access, responsive layouts, and stable visual evidence. Use for browser bugs, end-to-end UI behavior, responsive or accessibility checks, and screenshot baselines. Not for static source review without a…
pdlc-quality
Skill "pdlc-quality" from kanfu-panda/pdlc-skills, covering 质量闸门与报告, 这个命令的立身之本, 前置：两份真源, --init：首次建立目标声明 and 段一：跑真实 check.
e2e
Selects and runs the appropriate AgentsMesh end-to-end suite for Web, Desktop, MCP, or iOS, including worktree-specific environment setup and browser-level verification. Use when a change needs E2E coverage, a user asks to execute or diagnose an E2E test, or a cross-service workflow must be verified against the real…