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.
git clone --depth 1 https://github.com/xiaozhi86/qamasterWrote 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/rules/xiaozhi86/qamaster/case-design)<a href="https://agentmods.dev/rules/xiaozhi86/qamaster/case-design"><img src="https://agentmods.dev/badge/rules/xiaozhi86/qamaster/case-design/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/rules/xiaozhi86/qamaster/case-design"><img src="https://agentmods.dev/badge/rules/xiaozhi86/qamaster/case-design.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00147 |
| Opus 5.5 | $0.00014 | $0.00059 |
| Sonnet 5.5 | $0.00007 | $0.00029 |
| Haiku 4.5 | $0.00003 | $0.00015 |
Grade A, and why
case-design 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 1mo 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.
What it actually says
你是 case-design skill。当用户要做测试用例设计 / 用例生成 / 需求转用例 / 用例转 Excel / 覆盖分析时，读取并严格执行 skills/case-design/SKILL.md，以该文件所在目录为 skill 根（references/、scripts/、config/ 均相对它解析），按其中 15 阶段流程工作，产出写入项目根的 case-design-out/。
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.
- 1mo ago First seen · 7 lines · 34 tokens per session scan A 30f8372186b8
case-design is a cursor rule published in the GitHub repository xiaozhi86/qamaster (5 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 147 once invoked, about $0.0001 per session on Opus 5.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-31.
Other cursor rules, from other repositories
pdf-viewer-and-annotator-architecture
When working on pdf annotations or pdf rendering, consult this high level overview.
test-document-knowledge-base
When testing or our pdf.js annotations.
langsmith_evaluation
Comprehensive guide for LangSmith evaluation with @google/genai, including setup, dataset creation, target functions, evaluators, and running evaluations.
testing-guide
A guide to testing software and checking code quality.
spec-for-ut
Unit testing is essential to ensure the reliability and stability of code, especially for React components and functions. Adhering to best practices and ensuring high test coverage is critical to maintaining a robust codebase.
unit-test-manners
When implementing unit tests, adhere to the following principles to ensure robust, maintainable, and fast tests.