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 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/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/garagon/nanostack/qa"><img src="https://agentmods.dev/badge/skills/garagon/nanostack/qa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 148 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00054 | $0.03149 |
| Opus 5.5 | $0.00022 | $0.01260 |
| Sonnet 5.5 | $0.00011 | $0.00630 |
| 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 1mo 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/qa — Quality Assurance & Debugging
You verify behavior and report reproducible findings. Do not edit product files or commit fixes during QA. Return repairs to the caller's build step, after all verification readers have stopped. A standalone QA invocation ends with the report, not a repair or publication.
Read-only means no product mutation, not side-effect-free execution: tests, browsers, and builds can write files or change services. Use disposable fixtures and dedicated temporary/results directories. Do not regenerate tracked snapshots, run migrations on shared data, or test production. If isolation is unavailable, report the affected checks as untested. Follow the active host's permissions; never bypass a guard to produce test output.
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 |
|---|---|---|
| Quick | --quick |
Happy path only, screenshots on failure only |
| Standard | (default) | Happy path + error states + empty states |
| Thorough | --thorough |
Happy + error + edge + load + regression tests |
| Report only | --report-only |
Same scope as standard; no automatic continuation |
--report-only remains supported with any intensity. All QA modes report findings without repairing product code.
WTF-Likelihood Heuristic
Describe regression concerns from observed failures and coverage gaps. The legacy wtf_likelihood field is qualitative, not a measured probability; do not invent percentages or a numeric safety score.
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.
- 1mo ago Changed · +1 lines e8ead9aecccd
- 1mo ago First seen · 290 lines · 54 tokens per session scan A 0dffd3e55baf
qa is a skill published in the GitHub repository garagon/nanostack (207 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 3,149 once invoked, about $0.0002 per session on Opus 5.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
ring:test-driven-development
Enforcing the RED-GREEN-REFACTOR loop: write one failing test and watch it fail, write minimal code to pass, then refactor green. Use when starting implementation of a new feature or bugfix, or writing any new production code. Requires pasted failure output as proof of RED; code written before its test must be…
ring:detecting-goroutine-leaks
Detecting goroutine leaks in Go: greps for goroutine patterns, audits goleak coverage (VerifyTestMain/VerifyNone), runs goleak, and dispatches ring:backend-go to fix leaks and add regression tests. Use after implementation or during review when code spawns goroutines or a leak is suspected. Runs before…
pasteurize
Diagnose and fix a hard bug. Build a reliable reproduction, name the cause, add a regression test, and apply the minimum fix. Use when the user reports a bug, a failure, a flaky test, a performance regression, an error, or a wrong result whose cause is unknown. Use when the user pastes a symptom, a stack trace, or…
debug
Systematic bug investigation with a five-phase framework: reproduce, narrow, diagnose, fix, verify. Supports automated regression bisect via --regression flag. Produces a structured debug report with root cause analysis, regression test, and CQ/Q self-evaluations.
write-e2e
Generate Playwright E2E tests from codebase analysis. Discovers routes, scores user flows by criticality, writes .spec.ts files that assert causality, and reports what was actually proven: GENERATED, STATICCHECKED, VERIFIEDLOCAL or VALIDATEDLIVE. Modes: --scope , --flow , --output , --base-url , --max-flows N, --live…
qa
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a…