wize-tea-risk

A risk-ranking guide that scores areas by probability and impact, then groups them into high- and low-risk work. High-risk areas receive deeper test design, while low-risk areas receive basic checks.

In plain words
What is it for?
Use it to plan testing priorities for a feature or story. It helps decide where to write detailed tests and where a smoke test—a quick basic check—is enough.
Why use it?
It prevents every part of a story from receiving the same testing effort. This focuses detailed testing on failures that are more likely or more damaging.

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/qwize-br/wize-development-kit/wize-tea-risk
Clone the repo
git clone --depth 1 https://github.com/qwize-br/wize-development-kit

Made for: Cursor.

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,437 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00006 $0.01437
Opus 5 $0.00003 $0.00718
Sonnet 5 $0.00001 $0.00287
Haiku 4.5 $0.00001 $0.00144

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

Security

Grade A, and why

wize-tea-risk 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 3d 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/wize-tea-risk.mdc · 139 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 3d ago First seen · 139 lines · 6 tokens per session scan A 3fed1310b2fa

Subscribe to this mod's changes

wize-tea-risk is a cursor rule published in the GitHub repository qwize-br/wize-development-kit (12 stars, last pushed 5d ago), with no licence file. It adds 6 tokens to every session and 1,437 once invoked, about $0.0000 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.