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/release-analyze)<a href="https://agentmods.dev/rules/katalon-labs/true-skills/release-analyze"><img src="https://agentmods.dev/badge/rules/katalon-labs/true-skills/release-analyze.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.00107 | $0.02233 |
| Opus 5 | $0.00053 | $0.01117 |
| Sonnet 5 | $0.00021 | $0.00447 |
| Haiku 4.5 | $0.00011 | $0.00223 |
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 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 — 244 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 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 · 244 lines · 107 tokens per session scan A cacfa9304bc3
release-analyze is a cursor rule published in the GitHub repository katalon-labs/true-skills (7 stars, last pushed 13d ago), licensed MIT. It adds 107 tokens to every session and 2,233 once invoked, about $0.0005 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.