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-exploratory-testinggit 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-exploratory-testing)<a href="https://agentmods.dev/skills/kokxi/qa-test-skills/qa-exploratory-testing"><img src="https://agentmods.dev/badge/skills/kokxi/qa-test-skills/qa-exploratory-testing.svg" alt="Measured on agentmods" 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.00113 | $0.02657 |
| Opus 5 | $0.00056 | $0.01328 |
| Sonnet 5 | $0.00023 | $0.00531 |
| Haiku 4.5 | $0.00011 | $0.00266 |
Grade A, and why
qa-exploratory-testing 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ 安全警告：本技能的示例可能涉及订单号、支付金额、截图、身份证、手机号等敏感数据。 实际使用时请勿粘贴真实生产数据、客户信息或财务凭证；测试前应脱敏/掩码处理。 本技能仅在 workspace/ 输出评估文件，不持久化、不外传、不跨会话复用。
探索式测试
核心原则
探索式测试不是随意测试，而是有章程、有记录、有学习的系统化探索。 本技能基于SBTM框架（Session-Based Test Management）进行结构化探索。
深度要求（参考值）
关键指标：根据功能复杂度调整探索深度
| 复杂度 | Session要求 | Bug发现目标 | 说明 |
|---|---|---|---|
| 简单功能 | 1-2个Session | 3-5个发现 | 单一功能/页面 |
| 中等功能 | 3-5个Session | 8-15个发现 | 多页面/流程功能 |
| 复杂功能 | 5-8个Session | 15-30个发现 | 跨模块/核心业务流 |
Session-Based Test Management（SBTM）
Charter（测试章程）
Charter结构：
├─ 探索（Explore）
├─ 学习（Learn）
├─ 关于（About）
├─ 使用（Using）
├─ 发现（Discover）
└─ 信息（Information）
示例：
"探索用户登录功能，学习它如何处理异常输入，
使用边界值和特殊字符，发现潜在的安全漏洞和用户体验问题。"
Session类型
├─ 探索Session：发现新问题
│ ├─ 时长：60-120分钟
│ ├─ 目标：发现新Bug、新风险
│ └─ 记录：发现、问题、疑问
│
├─ 评审Session：验证修复
│ ├─ 时长：30-60分钟
│ ├─ 目标：验证Bug修复、回归测试
│ └─ 记录：验证结果、遗留问题
│
└─ 调研Session：技术调研
├─ 时长：60-120分钟
├─ 目标：了解系统、评估可测试性
└─ 记录：系统架构、技术细节
漫游测试方法
1. 卖点漫游（Feature Tour）
方法：
├─ 从用户视角体验所有功能
├─ 记录每个功能的使用感受
├─ 发现功能设计问题
└─ 评估用户体验
关注点：
├─ 功能是否易用？
├─ 功能是否符合预期？
├─ 功能间是否一致？
└─ 有无设计缺陷？
2. 地标漫游（Landmark Tour）
方法：
├─ 识别系统的关键入口/出口
├─ 从每个入口深入探索
├─ 发现入口/出口相关问题
└─ 验证系统导航
关注点：
├─ 入口是否清晰？
├─ 导航是否合理？
├─ 返回/退出是否正常？
└─ 状态是否正确保存？
3. 旅伴漫游（Bad Neighborhood）
方法：
├─ 识别系统的问题高发区
├─ 重点探索这些问题区域
├─ 发现历史问题的根源
└─ 验证改进效果
关注点：
├─ 历史Bug集中的模块
├─ 复杂度高的代码
├─ 频繁变更的功能
└─ 用户投诉多的区域
4. 基于风险的漫游（Risk Tour）
方法：
├─ 识别高风险区域
├─ 设计针对性探索策略
├─ 深入测试高风险场景
└─ 验证风险控制措施
关注点：
├─ 资金相关功能
├─ 安全相关功能
├─ 核心业务流程
└─ 第三方集成
角色扮演测试
用户角色
角色类型：
├─ 新手用户：第一次使用
│ ├─ 关注：学习成本、引导设计
│ └─ 探索：误操作、困惑点
│
├─ 普通用户：日常使用
│ ├─ 关注：效率、稳定性
│ └─ 探索：常用路径、痛点
│
├─ 专家用户：高频使用
│ ├─ 关注：效率、高级功能
│ └─ 探索：快捷键、批量操作
│
└─ 恶意用户：异常使用
├─ 关注：安全、稳定性
└─ 探索：注入、越权、破坏
角色卡片模板
## 角色卡片
### 基本信息
- 角色名称：[名称]
- 使用频率：[每天/每周/偶尔]
- 技术水平：[新手/普通/专家]
- 核心诉求：[最关心什么]
### 使用场景
- 典型操作：[日常操作]
- 使用时间：[工作时间/随时随地]
- 使用设备：[PC/手机/平板]
### 痛点预期
- 常见问题：[可能遇到的问题]
- 不满点：[可能不满意的地方]
- 误操作：[可能的误操作]
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 b866efe92839
- 8d ago First seen · 288 lines · 113 tokens per session scan A 5180d6586aa7
qa-exploratory-testing is a skill published in the GitHub repository Kokxi/qa-test-skills (24 stars, last pushed 5d ago), licensed MIT. It adds 113 tokens to every session and 2,657 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.
swarm-advanced
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows.
react-development
React 19+ with TypeScript — hooks, custom hooks, state management (useState/useReducer/useContext), React Query/SWR, Tailwind CSS, performance. Use when building React components, apps, or optimizing renders.