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/commands/katalon-labs/true-skills/test-management)<a href="https://agentmods.dev/commands/katalon-labs/true-skills/test-management"><img src="https://agentmods.dev/badge/commands/katalon-labs/true-skills/test-management/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/commands/katalon-labs/true-skills/test-management"><img src="https://agentmods.dev/badge/commands/katalon-labs/true-skills/test-management.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.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 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.
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.
- 2d ago First seen · 98 lines · 124 tokens per session scan A ddf4177eb43b
test-management is a command published in the GitHub repository katalon-labs/true-skills (8 stars, last pushed today), 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-09-08.
Other commands, from other repositories
implement
Execute tasks from a track's implementation plan following TDD workflow.
status
Display project status, active tracks, and next actions.
manage
Manage track lifecycle: archive, restore, delete, rename, and cleanup.
backlot
Open the Backlot living storyboard — the browser board that shows pipeline stages, script, scene plan, and generated assets live as a production runs.
aqa-flow
Router workflow for test automation: routes to ui-aqa-flow, api-aqa-flow, or testgen-flow. Kept for backward compatibility.
sddp-implement-qc-loop
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.