wize-tea-trace

wize-tea-trace is a cursor rule for Cursor from qwize-br/wize-development-kit. It costs 22 tokens per session (955 once invoked), scanned A, original, no licence file.

A test-tracing guide that connects every acceptance criterion—the condition a user story must meet—to one or more concrete tests in the code repository. It reports whether each criterion is covered, partly covered, or missing.

In plain words
What is it for?
Use it to review test coverage for user stories before approval. It helps find missing tests and incomplete links between requirements and the repository’s tests.
Why use it?
It shows whether the promised behaviour is actually tested. This prevents a story from being approved when important requirements have no test.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to review test coverage for user stories before approval. It helps find missing tests and incomplete links between requirements and the repository’s tests.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/qwize-br/wize-development-kit/wize-tea-trace
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.

Clone the repo
git clone --depth 1 https://github.com/qwize-br/wize-development-kit

Made for: Cursor.

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

agentmods badge for wize-tea-trace

README.md
[![agentmods](https://agentmods.dev/badge/rules/qwize-br/wize-development-kit/wize-tea-trace/github.svg)](https://agentmods.dev/rules/qwize-br/wize-development-kit/wize-tea-trace)
Your own site
<a href="https://agentmods.dev/rules/qwize-br/wize-development-kit/wize-tea-trace"><img src="https://agentmods.dev/badge/rules/qwize-br/wize-development-kit/wize-tea-trace/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.

agentmods 80×15 button for wize-tea-trace

Your own site · 80×15
<a href="https://agentmods.dev/rules/qwize-br/wize-development-kit/wize-tea-trace"><img src="https://agentmods.dev/badge/rules/qwize-br/wize-development-kit/wize-tea-trace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 955 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00022 $0.00955
Opus 5.5 $0.00009 $0.00382
Sonnet 5.5 $0.00004 $0.00191
Haiku 4.5 $0.00002 $0.00096

Measured today against content hash c67f424d3d7d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wize-tea-trace 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 today.

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-trace.mdc · 107 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

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. today Changed · +16 tokens per session c67f424d3d7d
  2. 1mo ago First seen · 107 lines · 6 tokens per session scan A 905c60f4324e

Subscribe to this mod's changes

wize-tea-trace is a cursor rule published in the GitHub repository qwize-br/wize-development-kit (19 stars, last pushed yesterday), with no licence file. It adds 22 tokens to every session and 955 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-30.