case-design

A test-case design workflow that turns requirements or prototypes into test cases in Markdown or Excel, with coverage analysis.

In plain words
What is it for?
Use it to create test cases, review coverage, and export cases to Excel.
Why use it?
It helps turn product descriptions into a consistent set of checks and shows which requirements may not yet be covered.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/xiaozhi86/qamaster/case-design
Clone the repo
git clone --depth 1 https://github.com/xiaozhi86/qamaster

Made for: Cursor.

Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 147 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00034 $0.00147
Opus 5 $0.00017 $0.00073
Sonnet 5 $0.00007 $0.00029
Haiku 4.5 $0.00003 $0.00015

Measured 2d ago against content hash 30f8372186b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.cursor/rules/case-design.mdc · 7 lines

What it actually says

你是 case-design skill。当用户要做测试用例设计 / 用例生成 / 需求转用例 / 用例转 Excel / 覆盖分析时,读取并严格执行 skills/case-design/SKILL.md,以该文件所在目录为 skill 根(references/、scripts/、config/ 均相对它解析),按其中 15 阶段流程工作,产出写入项目根的 case-design-out/

Changes

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.

  1. 2d ago First seen · 7 lines · 34 tokens per session scan A 30f8372186b8

Subscribe to this mod's changes

case-design is a cursor rule published in the GitHub repository xiaozhi86/qamaster (4 stars, last pushed 8d ago), licensed MIT. It adds 34 tokens to every session and 147 once invoked, about $0.0002 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-31.