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-management)<a href="https://agentmods.dev/rules/katalon-labs/true-skills/test-management"><img src="https://agentmods.dev/badge/rules/katalon-labs/true-skills/test-management.svg" alt="Measured on agentmods" 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.00124 | $0.01415 |
| Opus 5 | $0.00062 | $0.00707 |
| Sonnet 5 | $0.00025 | $0.00283 |
| Haiku 4.5 | $0.00012 | $0.00142 |
Grade A, and why
test-management 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 7d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Katalon Test Management
Use this skill for the management stage: keep the test inventory organized, findable, and fully traceable to requirements. Traceability is the platform's differentiator, so the headline output is a requirement <-> test case <-> suite map, not just folder tidying.
Availability Boundary
- Available via MCP: folders (
find_test_folders,manage_test_folder), suites (find_test_suites,manage_test_suite,read_test_suite), case organization (move_test_case,duplicate_test_case,delete_test_case), search (find_test_cases), and requirement links (link_requirements_to_test_case,unlink_requirements_from_test_case,find_test_cases_by_requirement,fetch_requirement_data). - Not directly available: custom fields and tags authoring, dynamic test suites, Git repository configuration, script-repo upload, and project governance/notifications — these are TestOps-UI or Studio operations. Name them as boundaries; do not claim MCP writes for them.
- Naming charset: test case names allow only letters, numbers, spaces and
( ) . , _ -. Folder paths allow/. Preferupdate/moveover delete-and-recreate (delete_test_casehas been unreliable).
Traceability Workflow
+---------------------+ +-----------------------+ +----------------------+
| Read requirements | --> | Map cases <-> reqs | --> | Find orphans + gaps |
+---------------------+ +-----------------------+ +----------------------+
| | |
v v v
+---------------------+ +-----------------------+ +----------------------+
| Link/unlink to fix | --> | Organize into suites | --> | Report traceability |
+---------------------+ +-----------------------+ +----------------------+
Steps and tool rules
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.
- 7d ago First seen · 98 lines · 124 tokens per session scan A 89385bf53be8
test-management is a cursor rule published in the GitHub repository katalon-labs/true-skills (7 stars, last pushed 12d ago), licensed MIT. It adds 124 tokens to every session and 1,415 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.
minimax-m3-status-verification
MiniMax M3 status and verification contract: exact claim labels, proof matching, multimodal-grounded visual claims, and evidence-first closeouts.
minimax-m3-verification
Extended M3 verification playbook: proof selection, multimodal-grounded checks, shell checks, browser checks, and recovery loops.
qa-engineer
Cursor rule "qa-engineer" from ulises-jeremias/agent-toolkit, covering qa engineer, responsibility, main skill domains, when invoked and delegate to skills.
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).
testing
Optional Spring Boot example-pack testing rules. Apply only when editing an adopted project or spring-boot profile output.