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-testability-advocacygit 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-testability-advocacy)<a href="https://agentmods.dev/skills/kokxi/qa-test-skills/qa-testability-advocacy"><img src="https://agentmods.dev/badge/skills/kokxi/qa-test-skills/qa-testability-advocacy/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-testability-advocacy"><img src="https://agentmods.dev/badge/skills/kokxi/qa-test-skills/qa-testability-advocacy.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.00166 | $0.02458 |
| Opus 5 | $0.00083 | $0.01229 |
| Sonnet 5 | $0.00033 | $0.00492 |
| Haiku 4.5 | $0.00017 | $0.00246 |
Grade A, and why
qa-testability-advocacy 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 6d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
可测试性推动
核心原则
在架构评审阶段就能识别可测试性问题，推动开发做可测试设计。
可测试性检查维度
维度1：接口层可测试性
检查点：
├─ Mock点：是否有Mock接口？
│ ├─ 外部依赖是否可Mock
│ ├─ 第三方服务是否可Mock
│ └─ 数据库是否可Mock
│
├─ 测试接口：是否有测试专用接口？
│ ├─ 数据初始化接口
│ ├─ 数据清理接口
│ └─ 状态查询接口
│
├─ 接口文档：接口文档是否完整？
│ ├─ 入参/出参定义
│ ├─ 错误码定义
│ └─ 示例数据
│
└─ 接口版本：接口版本管理？
├─ 向后兼容
└─ 版本切换
维度2：数据层可测试性
检查点：
├─ 数据构造：测试数据能否方便构造？
│ ├─ 数据工厂模式
│ ├─ 测试数据生成器
│ └─ 批量数据导入
│
├─ 数据清理：测试数据能否方便清理？
│ ├─ 测试后自动清理
│ ├─ 按用例隔离
│ └─ 按模块隔离
│
├─ 数据隔离：测试数据能否隔离？
│ ├─ 测试环境独立
│ ├─ 测试库独立
│ └─ 测试账户独立
│
└─ 数据查询：能否方便查询数据状态？
├─ 数据状态查询接口
├─ 数据变更日志
└─ 数据快照
维度3：日志层可测试性
检查点：
├─ 关键路径日志：关键操作是否有日志？
│ ├─ 业务操作日志
│ ├─ 数据变更日志
│ └─ 异常处理日志
│
├─ 日志级别：日志级别是否合理？
│ ├─ DEBUG：调试信息
│ ├─ INFO：业务信息
│ ├─ WARN：警告信息
│ └─ ERROR：错误信息
│
├─ TraceId：是否有链路追踪？
│ ├─ 请求唯一标识
│ ├─ 跨服务追踪
│ └─ 日志关联
│
└─ 日志查询：能否方便查询日志？
├─ 日志平台
├─ 日志搜索
└─ 日志分析
维度4：配置层可测试性
检查点：
├─ 功能开关：是否有功能开关？
│ ├─ 新功能开关
│ ├─ 实验功能开关
│ └─ 灰度开关
│
├─ 配置动态化：配置能否动态修改？
│ ├─ 运行时配置
│ ├─ 热更新配置
│ └─ 配置回滚
│
├─ 测试配置：是否有测试专用配置？
│ ├─ 测试环境配置
│ ├─ Mock配置
│ └─ 超时配置
│
└─ 配置文档：配置项文档是否完整？
├─ 配置项说明
├─ 默认值说明
└─ 影响范围说明
维度5：依赖层可测试性
检查点：
├─ 外部依赖：外部依赖能否Mock？
│ ├─ 第三方接口Mock
│ ├─ 消息队列Mock
│ └─ 缓存服务Mock
│
├─ 服务依赖：服务依赖能否隔离？
│ ├─ 服务虚拟化
│ ├─ 契约测试
│ └─ 集成测试环境
│
├─ 数据库依赖：数据库依赖能否Mock？
│ ├─ 内存数据库
│ ├─ 测试数据库
│ └─ 数据库快照
│
└─ 降级方案：依赖异常时能否降级？
├─ 熔断机制
├─ 降级策略
└─ 容错处理
可测试性评估表
| 维度 | 检查点 | 现状 | 目标 | 差距 | 改进措施 |
|---|---|---|---|---|---|
| 接口层 | Mock点 | 无 | 有 | 大 | 开发Mock接口 |
| 数据层 | 数据构造 | 手动 | 自动 | 中 | 开发数据工厂 |
| 日志层 | TraceId | 无 | 有 | 大 | 接入链路追踪 |
| 配置层 | 功能开关 | 无 | 有 | 中 | 开发开关平台 |
| 依赖层 | 服务Mock | 无 | 有 | 大 | 开发服务虚拟化 |
可测试性改进建议
短期改进（1-2周）
├─ 接口层：添加测试接口
├─ 数据层：编写数据构造脚本
├─ 日志层：添加关键路径日志
├─ 配置层：添加测试配置项
└─ 依赖层：配置Mock数据
中期改进（1-2月）
├─ 接口层：开发Mock平台
├─ 数据层：开发数据工厂
├─ 日志层：接入链路追踪
├─ 配置层：开发开关平台
└─ 依赖层：开发服务虚拟化
长期改进（3-6月）
├─ 接口层：契约测试平台
├─ 数据层：测试数据管理平台
├─ 日志层：日志分析平台
├─ 配置层：配置中心
└─ 依赖层：服务治理平台
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.
- 6d ago Changed 19f354cfafac
- 11d ago First seen · 249 lines · 166 tokens per session scan A 757d1366fe67
qa-testability-advocacy is a skill published in the GitHub repository Kokxi/qa-test-skills (25 stars, last pushed 9d ago), licensed MIT. It adds 166 tokens to every session and 2,458 once invoked, about $0.0008 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
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
swarm-advanced
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows.
code-review
Reviews Spec Kit code changes for positive and negative test coverage, regression evidence for bug fixes, and consistent repository terminology. Use when reviewing a diff or pull request. Do not use for implementing changes or posting GitHub review actions.
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.