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-shift-rightgit 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-shift-right)<a href="https://agentmods.dev/skills/kokxi/qa-test-skills/qa-shift-right"><img src="https://agentmods.dev/badge/skills/kokxi/qa-test-skills/qa-shift-right/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-shift-right"><img src="https://agentmods.dev/badge/skills/kokxi/qa-test-skills/qa-shift-right.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.00122 | $0.02494 |
| Opus 5 | $0.00061 | $0.01247 |
| Sonnet 5 | $0.00024 | $0.00499 |
| Haiku 4.5 | $0.00012 | $0.00249 |
Grade A, and why
qa-shift-right 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
测试右移实践
核心原则
测试右移——在生产环境验证质量，持续监控和改进。
⚠️ 安全警告：使用本技能前必须确认以下条件
生产环境操作: 本技能涉及灰度发布、线上监控、混沌工程等生产环境操作。执行前必须获得团队/组织的明确书面授权。
用户隐私: 涉及用户行为分析、埋点数据收集时，必须确保已获得用户知情同意，并符合数据保护法规（如GDPR/PIPL）要求。
爆炸半径控制: 混沌工程实验必须先在小范围（非生产/影子环境）验证，逐步扩大。必须设置熔断机制和自动回滚，确保故障影响在可控范围内。
回滚预案: 任何灰度发布必须预先准备回滚方案，定义明确的回滚触发条件（错误率、业务指标异常阈值），并确保回滚流程经过演练。
禁止场景: 禁止在生产环境直接执行未经审批的混沌实验、禁止在未告知用户的情况下收集行为数据、禁止在无回滚方案的情况下全量发布。
右移阶段
阶段1：灰度发布
📌 本节与 qa-release-risk-governance「灰度策略设计」内容同步，修改时请同步更新两处。
灰度策略：
├─ 用户灰度
│ ├─ 内部员工 → 白名单用户 → 10% → 50% → 100%
│ ├─ 适用：新功能、高风险功能
│ └─ 监控：业务指标、错误率、用户反馈
│
├─ 流量灰度
│ ├─ 1% → 10% → 30% → 50% → 100%
│ ├─ 适用：性能优化、算法变更
│ └─ 监控：性能指标、资源使用
│
├─ 地域灰度
│ ├─ 某城市 → 某省份 → 全国
│ ├─ 适用：地域性功能
│ └─ 监控：地域指标、用户反馈
│
└─ 时间灰度
├─ 低峰期 → 高峰期
├─ 适用：定时任务、批处理
└─ 监控：执行结果、资源使用
灰度监控
监控指标：
├─ 业务指标
│ ├─ 订单量/交易量
│ ├─ 转化率/成功率
│ └─ 用户活跃度
│
├─ 技术指标
│ ├─ 错误率/异常率
│ ├─ 响应时间/吞吐量
│ └─ 资源使用率
│
└─ 用户反馈
├─ 投诉量
├─ 客服咨询量
└─ 社交媒体反馈
灰度回滚
回滚条件：
├─ 业务指标异常
│ ├─ 订单量下降 > 20%
│ ├─ 成功率下降 > 5%
│ └─ 用户投诉增加 > 50%
│
├─ 技术指标异常
│ ├─ 错误率 > 1%
│ ├─ 响应时间增加 > 50%
│ └─ CPU/内存使用率 > 80%
│
└─ 用户反馈异常
├─ 投诉量激增
└─ 负面舆情
阶段2：线上监控
监控体系：
├─ 业务监控
│ ├─ 核心业务指标
│ ├─ 业务流程监控
│ └─ 业务异常告警
│
├─ 技术监控
│ ├─ 应用性能监控（APM）
│ ├─ 基础设施监控
│ ├─ 日志监控
│ └─ 链路追踪
│
└─ 用户体验监控
├─ 前端性能监控
├─ 用户行为分析
└─ 用户反馈收集
监控工具
├─ APM工具
│ ├─ SkyWalking
│ ├─ Pinpoint
│ ├─ Jaeger
│ └─ Zipkin
│
├─ 日志工具
│ ├─ ELK Stack
│ ├─ Loki
│ └─ Splunk
│
├─ 告警工具
│ ├─ Prometheus + Alertmanager
│ ├─ Grafana
│ └─ PagerDuty
│
└─ 用户体验工具
├─ 前端监控：Sentry
├─ 用户行为：Mixpanel
└─ 用户反馈：Hotjar
阶段3：混沌工程
混沌工程原则：
├─ 稳态假设：系统在故障下应保持稳态
├─ 爆炸半径：控制故障影响范围
├─ 持续实验：持续验证系统韧性
└─ 自动化：自动化故障注入和恢复
故障类型：
├─ 基础设施故障
│ ├─ 网络延迟/丢包
│ ├─ 节点宕机
│ ├─ 磁盘故障
│ └─ CPU/内存压力
│
├─ 应用层故障
│ ├─ 服务不可用
│ ├─ 接口超时
│ ├─ 数据库故障
│ └─ 缓存故障
│
└─ 业务层故障
├─ 第三方服务故障
├─ 数据不一致
└─ 流量突增
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 ecd5b1607ff8
- 9d ago First seen · 253 lines · 122 tokens per session scan A a57ed18b7e1e
qa-shift-right is a skill published in the GitHub repository Kokxi/qa-test-skills (24 stars, last pushed 7d ago), licensed MIT. It adds 122 tokens to every session and 2,494 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
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…
ui5-best-practices-opa5
This skill should be used in any OPA5 task - creating, modifying, extending, debugging, fixing or reviewing an integration test. Use when the user asks to "write an OPA5 test", "add an OPA5 journey", "fix the OPA5 test failure" or mentions OPA5 or its components - opaTest, page object, journey, waitFor.
webapp-testing
Test local web applications using browser automation - verify frontend functionality, debug UI behavior, capture screenshots, view console logs, run E2E scenarios, and check accessibility.
webapp-testing
Write and run comprehensive web app tests — unit, integration, E2E with Playwright/Cypress, and visual regression.
testing-patterns
Vitest + Playwright testing patterns: unit tests, mocking, fixtures, E2E, coverage, and anti-patterns. Use when writing tests, setting up test infrastructure, or following TDD workflows.
javascript-testing-patterns
Comprehensive guide for implementing robust testing strategies in JavaScript/TypeScript applications using modern testing frameworks and best practices.