A review workflow for checking the coverage, quality, reliability, and environment readiness of Katalon tests. It produces a decision about whether a suite is fit to enter the delivery pipeline.

Use it to review requirement and configuration coverage, inspect test-case quality, check stability and flakiness, and identify named cases that need attention.

It helps find missing coverage, weak test design, unstable cases, and unsuitable environments before they affect a release. It gives a verdict instead of leaving you with disconnected measurements.

test-review — Command for GitHub Copilot by katalon-labs

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/katalon-labs/true-skills

Made for: GitHub Copilot.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/katalon-labs/true-skills/test-review/github.svg)](https://agentmods.dev/commands/katalon-labs/true-skills/test-review)

Your own site

<a href="https://agentmods.dev/commands/katalon-labs/true-skills/test-review"><img src="https://agentmods.dev/badge/commands/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/katalon-labs/true-skills/test-review"><img src="https://agentmods.dev/badge/commands/katalon-labs/true-skills/test-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 126 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,274 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 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.

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

Measured 2d ago against content hash 926d1c084033, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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

.github/prompts/test-review.prompt.md · 103 lines

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_requirement for requirement coverage; fetch_test_configuration_data for browser/platform coverage. Flag orphan requirements and under-covered configurations.
Quality review. fetch_test_case_data for design signals; read representative cases with read_test_case when a signal is ambiguous. Flag non-atomic cases (many assertions), missing negative/boundary variants, and vague expected results.
Reliability review. fetch_test_stability_data for flakiness; find_test_results for recent pass/fail history. Flag probabilistically flaky cases that will erode pipeline trust.
Environment readiness. read_auts to 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.

Read the full file on GitHub · 103 lines

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.

2d ago First seen · 103 lines · 126 tokens per session scan A 926d1c084033

Subscribe to this mod's changes

test-review is a command published in the GitHub repository katalon-labs/true-skills (8 stars, last pushed yesterday), 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-09-08.

Claude Code Testing agent-skills agentic-ai ai-testing cursor github-copilot

test-review

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Katalon Test Review

Availability Boundary

Review Workflow

Steps and tool rules

What this file has done since we first saw it

Other commands, from other repositories

implement

test-review

run_tests

write-unit-tests

test

implement_tests