Borrowing it
Nothing to install: this file belongs to rakovi4/continue-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rakovi4/continue-framework/main/.claude/skills/qa-run/SKILL.mdgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWrote 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/rakovi4/continue-framework/qa-run)<a href="https://agentmods.dev/skills/rakovi4/continue-framework/qa-run"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/qa-run/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/rakovi4/continue-framework/qa-run"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/qa-run.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.00080 | $0.01124 |
| Opus 5.5 | $0.00032 | $0.00450 |
| Sonnet 5.5 | $0.00016 | $0.00225 |
| Haiku 4.5 | $0.00008 | $0.00112 |
Grade A, and why
qa-run 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 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.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/qa-run - Run a Manual QA Checklist Against prod-copy
Drive the cases of a QA task (created by /task qa) against the live external
environment, one case at a time, in a headed browser the tester watches. Each
case either passes (tick the box) or fails (leave [ ], file a bug).
Executing the checklist also validates the checklist itself (the test model):
a case you cannot verify through the UI, or whose intent is ambiguous, is a defect
in the test model — fixed in the task spec.md — which is distinct from a product
defect, which becomes a /task bugfix.
Input
- target (optional): QA task number/slug. If absent, infer the in-progress QA task from the task progress files / recent git log.
Core Constraints
- UI-only navigation. Reach every page by clicking visible buttons, links, and
menu items — never type, paste, or script a direct in-app URL. The only allowed
direct-URL uses are the two carved out in
.claude/guidelines/frontend-rules.md("FORBIDDEN in-app navigation via URL"): the app root as the session entry point, and genuine external-arrival links a real user would click (an emailed verification or password-reset link). A manual tester must prove the same navigation paths a real user walks — the same constraint the Selenium rule applies to automated tests. - One action per step, watched. Connect to a headed browser the tester can see; perform a single action, then screenshot, then say what to look for. Never batch a whole case into one scripted run — the point is for the tester to watch each step.
- Real integrations, real creds. External-integration credentials (external-API
sandbox key, payment-gateway sandbox shop, mail inbox) come from
infrastructure/creds.txt(gitignored — NEVER commit) and from the tester as each case needs them. Never echo a secret into a committed file or a screenshot name. - Never block >30s (CLAUDE.md Interaction Rules). Long waits (a scheduler tick, email delivery) run in the background with short, separate polls (≤30s each).
- Read-only on infrastructure. prod-copy is a real environment — diagnose freely,
change nothing (see
.claude/rules/infrastructure.md). Read ports and base URLs from config; never hardcode them.
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 35e5a4b04771
- 2mo ago First seen · 82 lines · 80 tokens per session scan A 065ac5673824
qa-run is a skill published in the GitHub repository rakovi4/continue-framework (54 stars, last pushed 29d ago), licensed MIT. It adds 80 tokens to every session and 1,124 once invoked, about $0.0003 per session on Opus 5.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-08-30.
Other skills, from other repositories
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.