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 Kokxi/qa-test-skills --skill qa-test-reportinggit clone --depth 1 https://github.com/Kokxi/qa-test-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/kokxi/qa-test-skills/qa-test-reporting)<a href="https://agentmods.dev/skills/kokxi/qa-test-skills/qa-test-reporting"><img src="https://agentmods.dev/badge/skills/kokxi/qa-test-skills/qa-test-reporting/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/kokxi/qa-test-skills/qa-test-reporting"><img src="https://agentmods.dev/badge/skills/kokxi/qa-test-skills/qa-test-reporting.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.00110 | $0.02412 |
| Opus 5 | $0.00055 | $0.01206 |
| Sonnet 5 | $0.00022 | $0.00482 |
| Haiku 4.5 | $0.00011 | $0.00241 |
Grade A, and why
qa-test-reporting 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 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.
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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ 安全警告：本技能的示例可能涉及发布建议和延期结论字段。 这些是报告字段不是直接操作；请勿未经授权即执行发布或延期决策。 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。
测试报告编写
核心原则
测试报告不是数据堆砌，而是决策支持——让读者快速了解质量状态和风险。
报告类型
1. 日报
用途：每日测试进展同步
受众：测试团队、开发
频率：每日
内容结构：
├─ 今日完成
│ ├─ 用例执行：XX条
│ ├─ 缺陷发现：XX个
│ ├─ 缺陷修复：XX个
│ └─ 遗留问题：XX个
│
├─ 问题与风险
│ ├─ 阻塞问题：[描述]
│ ├─ 风险提示：[描述]
│ └─ 需要支持：[描述]
│
└─ 明日计划
├─ 测试重点：[描述]
└─ 预计产出：[描述]
2. 周报
用途：每周测试进展总结
受众：测试负责人、项目经理
频率：每周
内容结构：
├─ 本周概览
│ ├─ 用例执行率：XX%
│ ├─ 用例通过率：XX%
│ ├─ 缺陷发现数：XX个
│ ├─ 缺陷修复率：XX%
│ └─ 质量状态：[绿/黄/红]
│
├─ 详细数据
│ ├─ 按模块统计
│ ├─ 按严重程度统计
│ ├─ 按类型统计
│ └─ 趋势分析
│
├─ 问题与风险
│ ├─ 本周问题：[列表]
│ ├─ 遗留风险：[列表]
│ └─ 需要决策：[列表]
│
└─ 下周计划
├─ 测试重点：[描述]
├─ 资源需求：[描述]
└─ 预计产出：[描述]
3. 迭代报告
用途：迭代测试总结
受众：项目团队、管理层
频率：每个迭代结束
内容结构：
├─ 执行摘要
│ ├─ 迭代目标：[描述]
│ ├─ 测试范围：[描述]
│ ├─ 质量结论：[通过/有条件通过/不通过]
│ └─ 发布建议：[建议发布/建议延期]
│
├─ 质量数据
│ ├─ 用例统计
│ │ ├─ 总用例数：XX
│ │ ├─ 执行用例数：XX
│ │ ├─ 通过用例数：XX
│ │ ├─ 执行率：XX%
│ │ └─ 通过率：XX%
│ │
│ ├─ 缺陷统计
│ │ ├─ 新增缺陷：XX个
│ │ ├─ 已修复：XX个
│ │ ├─ 遗留缺陷：XX个
│ │ ├─ 严重缺陷：XX个
│ │ └─ 缺陷修复率：XX%
│ │
│ └─ 质量指标
│ ├─ 需求覆盖率：XX%
│ ├─ 代码覆盖率：XX%
│ ├─ 缺陷密度：XX/功能点
│ └─ 漏测率：XX%
│
├─ 风险评估
│ ├─ 高风险区域：[列表]
│ ├─ 遗留问题：[列表]
│ └─ 修复建议：[列表]
│
├─ 改进建议
│ ├─ 流程改进：[建议]
│ ├─ 工具改进：[建议]
│ └─ 能力提升：[建议]
│
└─ 附件
├─ 用例执行明细
├─ 缺陷清单
└─ 质量趋势图
4. 专项报告
类型：
├─ 性能测试报告
├─ 安全测试报告
├─ 兼容性测试报告
├─ 接口测试报告
└─ 探索测试报告
内容结构：
├─ 测试目标
├─ 测试范围
├─ 测试环境
├─ 测试方法
├─ 测试结果
│ ├─ 通过项
│ ├─ 失败项
│ └─ 风险项
├─ 问题分析
└─ 结论建议
报告模板
测试日报模板
# 测试日报
**日期**：YYYY-MM-DD
**报告人**：[姓名]
**项目**：[项目名称]
## 今日完成
| 项目 | 数量 | 备注 |
|------|------|------|
| 用例执行 | XX条 | |
| 缺陷发现 | XX个 | |
| 缺陷修复 | XX个 | |
| 遗留问题 | XX个 | |
## 问题与风险
- [ ] 阻塞问题：[描述]
- [ ] 风险提示：[描述]
- [ ] 需要支持：[描述]
## 明日计划
- 测试重点：[描述]
- 预计产出：[描述]
迭代报告模板
# 迭代测试报告
## 执行摘要
| 指标 | 结果 | 目标 | 状态 |
|------|------|------|------|
| 用例执行率 | XX% | ≥95% | ✅/❌ |
| 用例通过率 | XX% | ≥90% | ✅/❌ |
| 缺陷修复率 | XX% | ≥95% | ✅/❌ |
| 严重缺陷 | XX个 | 0 | ✅/❌ |
## 质量结论
[通过/有条件通过/不通过]
## 发布建议
[建议发布/建议延期]
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 Changed f585c0a5d405
- 9d ago First seen · 263 lines · 110 tokens per session scan A 25c37dd736db
qa-test-reporting is a skill published in the GitHub repository Kokxi/qa-test-skills (24 stars, last pushed 7d ago), licensed MIT. It adds 110 tokens to every session and 2,412 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
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
octocode-benchmark
Use when planning, running, grading, or reporting the by-hand Octocode research benchmark — pairwise matchups (Octocode anchor vs one baseline: gh+RTK, gh+Headroom, or plain gh) over markdown questions, with a fresh isolated runner agent per (question, arm, pass), one blind judge per question grading two answers X/Y…
octocode-graph-eval
Use when you need a measurable keep/discard loop — goal→KPI, baseline vs target, held-out checks, eval suites, or don't-stop-till-done against a runnable sensor. Not for ordinary ship checks where 'tests passed' is enough.
plugin-test
A testing guide for Zhin.js plugins using Vitest, a JavaScript and TypeScript testing framework. It focuses on checking command and tool behavior, ordinary business logic, and the plugin package’s required structure.
modernize-test-starter
Modernize QUnit unit tests and OPA5 integration tests to the UI5 Test Starter concept. Use this skill when: The linter reports prefer-test-starter for .qunit.html or .qunit.js files Test HTML files use manual sap-ui-core.js bootstrapping instead of Test Starter's runTest.js/createSuite.js Test JS files use…
aiox-qa
Activate Quinn (qa) for Test Architect & Quality Advisor. Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including requirements traceability, risk assessment, and...