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/fishzjp/qa-skills/qanpx skills add fishzjp/qa-skills --skill qagit clone --depth 1 https://github.com/fishzjp/qa-skillsWrote 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/fishzjp/qa-skills/qa)<a href="https://agentmods.dev/skills/fishzjp/qa-skills/qa"><img src="https://agentmods.dev/badge/skills/fishzjp/qa-skills/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.00111 | $0.03110 |
| Opus 5 | $0.00056 | $0.01555 |
| Sonnet 5 | $0.00022 | $0.00622 |
| Haiku 4.5 | $0.00011 | $0.00311 |
Grade A, and why
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 2d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA 编排入口（qa）
把"帮我测试这个需求"翻译成一条可断点续跑的流水线。本 skill 是薄编排：不含任何测试方法与框架知识（全部在阶段 skill 与 core/），不替用户做裁决。
When to Use
- "帮我测试这个需求 / 功能"、"把这个功能完整过一遍"、"从需求到报告走一遍完整测试"
- 之前的流水线中断了，需要从落盘产物续跑
When NOT to Use
- 只要单阶段产出 → 对应阶段 skill：需求建模
requirement-analysis、测试策略test-strategy、写用例test-case-writing、审查已有用例test-case-review、E2E 执行automated-e2e-testing、API 执行api-testing、探索会话exploratory-testing、Bug 根因bug-analysis、回归范围regression-testing - 编写/修改某个阶段 skill 自身的方法论 → 不经过本 skill
编排会话模型（阶段间上下文隔离）
- 每个阶段运行在独立上下文中（宿主支持子会话/子代理时）：只加载当前阶段 skill 的 SKILL.md + 按需 references + 上一阶段的落盘产物文件；任一时刻活跃指令 ≤ 1–2 个 skill（当前阶段 + 本编排）
- 主会话只持有流水线状态：阶段清单、各产物文件路径、检查点状态——不加载任何阶段 skill 的领域知识
- 降级路径：宿主不支持子会话、或用户在单会话内手动走流水线时，退化为顺序会话 + 落盘文件衔接——正确性不受影响（状态全在文件里），损失的只是上下文卫生
- 反模式：单会话内顺序累加加载全部 SKILL.md（9 个 × 数百行指令同时在场）
- 注入式形态的例外：预注入部署（评测或宿主一次性注入全部指令）下本节隔离机制不存在——此时靠阶段顺序防串扰：任一时刻只执行当前阶段的指令，其余在场文件视为未加载；"文件即流水线状态"的原则两形态通用（双形态声明见
../core/evidence.md第 6 节）
流水线与落盘产物（文件即流水线状态）
| # | 阶段 | skill | 落盘产物 | 人工检查点 |
|---|---|---|---|---|
| 0 | （旁路，可选）探索先行 | exploratory-testing |
{项目}/探索笔记_{主题}.md |
— |
| 1 | 需求理解 | requirement-analysis |
{项目}/需求模型.md（含澄清记录） |
⏸ 澄清检查点：模糊/矛盾项等用户裁决 |
| 2 | 测试策略 | test-strategy |
{项目}/测试策略.md（Risk Map + 两域 scope 含 type_scope）+ 专项移交_{轴}_{日期}.yaml（有 handoff/blocked/外部执行器轴时） |
⏸ 预算裁决：full 预算裁剪触及 Critical 轴时呈现排序提案等用户裁决 |
| 3 | 用例编写 | test-case-writing |
{项目}/测试用例_markmap.md + 测试用例.schema.yaml |
— |
| 4 | 用例审查 | test-case-review |
修订后用例文件 + 审查记录（重新抽取 Schema） | — |
| 5 | 执行 | automated-e2e-testing / api-testing / 手动 |
自动路径：执行代码或脚本（playwright/ 或 API 测试脚本）+ 执行分报告 测试报告_{来源}_{日期}.md（命名见 ../core/report-template.md 头注；至少 §2 执行统计 + §3 Bug 清单条目，字段按 report-template）；手动路径 手动执行记录_{日期}.md |
⏸ 执行策略裁决：确认 automation_plan 提案（手动/e2e/api）；手动路径执行后 ⏸ 结果回收（TC × 结果） |
| 6 | Bug 分析 | bug-analysis（有已确认 Bug 时） |
中间产物 {项目}/Bug条目_{日期}.md（条目结构与根因分析等五个扩展字段按 report-template §3）——此阶段禁止新建或改写最终测试报告 |
⏸ Bug 定性检查点：预期 vs 缺陷 |
| 7 | 回归验证 | regression-testing（有代码变更/Bug 修复时） |
{项目}/回归清单_{日期}.md |
— |
| 8 | 收尾报告 | 本 skill（按 ../core/report-template.md） |
{项目}/测试报告_{日期}.md |
— |
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.
- 2d ago Changed · +11 lines 939f7a6ed4d8
- 6d ago First seen · 94 lines · 111 tokens per session scan A aea300bff5c3
qa is a skill published in the GitHub repository fishzjp/qa-skills (23 stars, last pushed 2d ago), licensed MIT. It adds 111 tokens to every session and 3,110 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
qa-expert
Expert-level quality assurance, testing strategies, automation, and QA processes. Use when the user mentions testing, test automation, quality assurance, or Selenium, or when the task involves Testing Types, QA Processes, Test Strategy, or Defect Management.
test-review
Ревью только что написанных или изменённых автотестов на соответствие best practices TypeScript + Playwright (по официальной документации) и конвенциям вашего проекта. Используй по /test-review либо после написания/правки любого теста (UI E2E, API, UI+API, моки, visual, mobile) или Page Object/фикстуры/констант — до…
playwright-expert
Expert in Playwright E2E testing framework, auto-waiting mechanisms, test generation, trace viewer, and CI/CD integration. Use when the user mentions testing, end-to-end tests, QA, automation, end-to-end testing, or test automation, or when the task involves Playwright Framework, Test Organization, Advanced Features…
selenium-expert
Expert in Selenium WebDriver, Selenium Grid, page object model, waits, cross-browser testing, and test automation frameworks. Use when the user mentions testing, end-to-end tests, QA, automation, WebDriver, or Selenium grid, or when the task involves Selenium Components, Browser Support, Advanced Features, or Basic…
playwright
When the user wants to design, implement, debug, stabilize, or scale Playwright tests. Use when the user mentions "Playwright," "playwright.config.ts," "page.locator," "page.getByRole," "browser context," "fixtures," "test.beforeEach," "trace viewer," "codegen," "Playwright Test," "Playwright MCP," "PWT," "WebKit…
appium
When the user wants to design, implement, debug, or scale Appium tests for iOS and Android mobile automation. Use when the user mentions "Appium," "Appium 2," "UiAutomator2," "XCUITest driver," "appium:capabilities," "AppiumServer," "accessibility id," "TouchAction," "W3C Actions," "Appium inspector," "real device…