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/katalon-labs/true-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/rules/katalon-labs/true-skills/test-review)<a href="https://agentmods.dev/rules/katalon-labs/true-skills/test-review"><img src="https://agentmods.dev/badge/rules/katalon-labs/true-skills/test-review/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/katalon-labs/true-skills/test-review"><img src="https://agentmods.dev/badge/rules/katalon-labs/true-skills/test-review.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.00126 | $0.01274 |
| Opus 5 | $0.00063 | $0.00637 |
| Sonnet 5 | $0.00025 | $0.00255 |
| Haiku 4.5 | $0.00013 | $0.00127 |
Grade A, and why
test-review 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 9d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Katalon Test Review
Use this skill for the review stage: inspect coverage, quality, and reliability so weak tests do not enter the pipeline. The output is a verdict with named weak cases, never a metric dump.
Availability Boundary
- Available via MCP: coverage review (
fetch_requirement_data,find_test_cases_by_requirement,fetch_test_configuration_data), quality review (fetch_test_case_data), reliability review (fetch_test_stability_data,find_test_results), and environment readiness (read_auts). - Not directly available: code/object review, local debug, StudioAssist Ask — these are Studio-desktop operations. For code-lane review, defer to
test-case-to-playwright/playwright-execute. Use Browser/Playwright only for AUT sanity checks when asked.
Review Workflow
+---------------------+ +----------------------+ +----------------------+
| Coverage review | --> | Quality review | --> | Reliability review |
| reqs + config | | case design signals | | flakiness/stability |
+---------------------+ +----------------------+ +----------------------+
|
v
+----------------------+
| Verdict + weak cases |
+----------------------+
Steps and tool rules
- Coverage review.
fetch_requirement_data+find_test_cases_by_requirementfor requirement coverage;fetch_test_configuration_datafor browser/platform coverage. Flag orphan requirements and under-covered configurations. - Quality review.
fetch_test_case_datafor design signals; read representative cases withread_test_casewhen a signal is ambiguous. Flag non-atomic cases (many assertions), missing negative/boundary variants, and vague expected results. - Reliability review.
fetch_test_stability_datafor flakiness;find_test_resultsfor recent pass/fail history. Flag probabilistically flaky cases that will erode pipeline trust. - Environment readiness.
read_autsto confirm an executable AUT exists for the suite. - Verdict. One of Approve / Approve with fixes / Reject for pipeline, followed by the specific cases to fix and why. State the risk if approving with known gaps.
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.
- 9d ago First seen · 103 lines · 126 tokens per session scan A 28c576878924
test-review is a cursor rule published in the GitHub repository katalon-labs/true-skills (8 stars, last pushed 2d ago), licensed MIT. It adds 126 tokens to every session and 1,274 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-31.
Other cursor rules, from other repositories
tdd-guide
Cursor rule "tdd-guide" from ulises-jeremias/agent-toolkit, covering agent vs skill rule — why agent (cite clause), when to use vs holistic, caller / skills / handoff, the tdd cycle and when invoked.
qa-engineer
Cursor rule "qa-engineer" from ulises-jeremias/agent-toolkit, covering qa engineer, responsibility, main skill domains, when invoked and delegate to skills.
minimax-m3-status-verification
MiniMax M3 status and verification contract: exact claim labels, proof matching, multimodal-grounded visual claims, and evidence-first closeouts.
e2e-runner
Cursor rule "e2e-runner" from ulises-jeremias/agent-toolkit, covering agent vs skill rule — why agent (cite clause), when to use vs holistic, caller / skills / handoff, when invoked and selector priority (most to least resilient).
fusebase-flow-validation
Fusebase Flow validation/verification phase rules. Use when running gate checks, reviewing diffs, or verifying smoke prompts.
testing
Optional Spring Boot example-pack testing rules. Apply only when editing an adopted project or spring-boot profile output.