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 release-analyzegit 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/release-analyze)<a href="https://agentmods.dev/skills/katalon-labs/true-skills/release-analyze"><img src="https://agentmods.dev/badge/skills/katalon-labs/true-skills/release-analyze/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/release-analyze"><img src="https://agentmods.dev/badge/skills/katalon-labs/true-skills/release-analyze.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.00111 | $0.01128 |
| Opus 5 | $0.00056 | $0.00564 |
| Sonnet 5 | $0.00022 | $0.00226 |
| Haiku 4.5 | $0.00011 | $0.00113 |
Grade A, and why
release-analyze 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 12d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Katalon Release Analyze
Use this skill to assess release readiness from Katalon MCP data. The output must be a testing-quality decision, not just a metric dump.
Availability Boundary
State the MCP boundary before promising an assessment:
- Available through Katalon MCP: project/repository discovery, requirements, test cases, test suites, executions/results, quality summaries, defect data, stability data, and configuration coverage when tools are exposed.
- Not directly available: create formal Test Plan entities, inspect live AUT UI, guarantee AI execution completion, or decide product/business readiness beyond test evidence.
- If MCP tools are unavailable, provide only a framework/template and mark release confidence as Low until data is verified.
Read references/capability-boundaries.md when capability scope is unclear.
Required Scope
Resolve or ask for the minimum missing scope:
- Katalon project and repository/Test Project.
- Release identifier, sprint, iteration, version, test suite, suite collection, execution ID, or date range.
- Target environment/configuration matrix when readiness depends on browsers, devices, OS, or deployment environments.
- Quality gate thresholds when the team has defined them.
If the user gives only a release name or issue key, use MCP discovery first. Ask only when multiple equally plausible scopes remain.
MCP Data Collection
Always resolve context before analysis:
- Call
list_projects. - Call
list_repositories. - Resolve the repository/Test Project.
- Find the release scope using available requirement, suite, execution, iteration, or result tools.
Collect evidence with the available Katalon MCP tools:
- Requirement and traceability:
find_requirements,read_requirement,fetch_requirement_data. - Test case quality:
find_test_cases,find_test_cases_by_requirement,fetch_test_case_data. - Suites and executable scope:
find_test_suites,read_test_suite. - Executions and results:
read_execution,read_execution_test_results,read_test_result,find_test_results. - Defect risk:
fetch_defect_data. - Stability:
fetch_test_stability_data. - Configuration coverage:
fetch_test_configuration_data.
What ships with it
2 files 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.
- 12d ago First seen · 125 lines · 111 tokens per session scan A 015a54309f62
release-analyze is a skill published in the GitHub repository katalon-labs/true-skills (8 stars, last pushed 3d ago), licensed MIT. It adds 111 tokens to every session and 1,128 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.