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.
npx skills add katalon-labs/true-skills --skill test-managementgit 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/skills/katalon-labs/true-skills/test-management)<a href="https://agentmods.dev/skills/katalon-labs/true-skills/test-management"><img src="https://agentmods.dev/badge/skills/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/skills/katalon-labs/true-skills/test-management"><img src="https://agentmods.dev/badge/skills/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.00127 | $0.00934 |
| Opus 5 | $0.00063 | $0.00467 |
| Sonnet 5 | $0.00025 | $0.00187 |
| Haiku 4.5 | $0.00013 | $0.00093 |
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 11d 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 — 51 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
- Establish scope.
list_projects->list_repositories. Resolve one target from context. - Build the trace map. For each requirement key,
find_test_cases_by_requirement; usefetch_requirement_datafor coverage status. Classify each requirement as: covered, partially covered, or orphan (no case). - Find loose assets.
find_test_casesby feature/folder/keyword to surface cases with no requirement link (orphan cases) and duplicates. - Fix links (only when known and requested).
link_requirements_to_test_caseafter requirement IDs are confirmed;unlink_requirements_from_test_casefor wrong links. Never guess a link. - Organize inventory.
manage_test_folderandmove_test_casefor structure;manage_test_suiteto group runnable cases. Reuse before creating; summarize bulk moves and get approval before executing them. - Report the traceability matrix. requirement -> case(s) -> suite(s), coverage %, orphan requirements, orphan cases, and duplicate candidates. This is the deliverable.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 51 lines · 127 tokens per session scan A d730af1c7a86
test-management is a skill published in the GitHub repository katalon-labs/true-skills (8 stars, last pushed yesterday), licensed MIT. It adds 127 tokens to every session and 934 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 skills, from other repositories
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
data-quality-frameworks
Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.