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-plangit 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-plan)<a href="https://agentmods.dev/skills/katalon-labs/true-skills/test-plan"><img src="https://agentmods.dev/badge/skills/katalon-labs/true-skills/test-plan/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-plan"><img src="https://agentmods.dev/badge/skills/katalon-labs/true-skills/test-plan.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.00140 | $0.00983 |
| Opus 5 | $0.00070 | $0.00491 |
| Sonnet 5 | $0.00028 | $0.00197 |
| Haiku 4.5 | $0.00014 | $0.00098 |
Grade A, and why
test-plan 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 10d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Katalon Test Plan
Use this skill for the planning stage of the Katalon lifecycle: turn quality goals into a scoped, risk-prioritized, executable plan. The output is a plan the team can act on plus the folder/suite/release structure that makes it runnable. Prefer Katalon MCP tools for platform data; use the human as a tool when scope, risk appetite, or release target cannot be resolved safely.
Availability Boundary
State the boundary before promising a plan:
- Available via MCP: resolve scope (
list_projects,list_repositories,find_iterations), read requirement coverage and gaps (fetch_requirement_data,find_requirements,find_test_cases_by_requirement), and build the executable plan structure (manage_test_folder,manage_test_suite, add cases to suites). - Not directly available: create a Release or Build entity, create a formal Test Plan entity, or author release gates through MCP. These live in the TestOps UI.
- Workaround (the MCP-legal test plan): a named folder + test suite associated with a sprint/release is the executable plan. Create it, populate it, and report it as the plan of record.
Planning Workflow
+---------------+ +----------------------+ +----------------------+
| Resolve scope | --> | Read coverage + risk | --> | Prioritize what first|
+---------------+ +----------------------+ +----------------------+
| | |
v v v
+---------------+ +----------------------+ +----------------------+
| Propose plan | --> | Build folder + suite | --> | Associate sprint/rel |
+---------------+ +----------------------+ +----------------------+
Steps and tool rules
- Resolve scope.
list_projects->list_repositories. If exactly one matches the user's wording or context, use it. Usefind_iterationsto bind the plan to a sprint/release when named. - Read coverage and gaps. Use
fetch_requirement_datafor requirement coverage status andfind_test_cases_by_requirementto see which requirements already have cases.find_requirements/read_requirementwhen requirement keys are supplied. - Prioritize by risk and evidence. Rank scope using: requirement coverage gaps first, then high-change/high-traffic areas, then areas with historically unstable tests (defer stability detail to
test-review). State the risk basis; do not invent traffic numbers the MCP does not return. - Propose the plan in chat. Objectives, in-scope / out-of-scope, coverage matrix (requirement -> planned cases), risk ranking, target environments, and the suite/folder structure you will create.
- Materialize the executable structure.
manage_test_folderfor the plan folder,manage_test_suitefor the runnable suite, add the selected/known cases. Reuse an existing folder/suite when one already matches instead of creating a duplicate. - Verify and report.
read_test_suiteto confirm; report the plan of record with the suite as the executable artifact and the open gaps to fill next.
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.
- 10d ago First seen · 54 lines · 140 tokens per session scan A be720bef914d
test-plan is a skill published in the GitHub repository katalon-labs/true-skills (8 stars, last pushed yesterday), licensed MIT. It adds 140 tokens to every session and 983 once invoked, about $0.0007 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.