Borrowing it
Nothing to install: this file belongs to katalon-labs/true-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/katalon-labs/true-skills/main/.kiro/steering/release-analyze.mdgit 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/instructions/katalon-labs/true-skills/release-analyze)<a href="https://agentmods.dev/instructions/katalon-labs/true-skills/release-analyze"><img src="https://agentmods.dev/badge/instructions/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/instructions/katalon-labs/true-skills/release-analyze"><img src="https://agentmods.dev/badge/instructions/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.02124 | $0.02124 |
| Opus 5.5 | $0.00850 | $0.00850 |
| Sonnet 5.5 | $0.00425 | $0.00425 |
| Haiku 4.5 | $0.00212 | $0.00212 |
Grade A, and why
true-skills release-analyze.md 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 1mo 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 — 243 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.
- 1mo ago First seen · 243 lines · 2,124 tokens per session scan A 1d2557ddeb20
true-skills release-analyze.md is an instructions file published in the GitHub repository katalon-labs/true-skills (10 stars, last pushed 4d ago), licensed MIT. It adds 2,124 tokens to every session, about $0.0085 per session on Opus 5.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 instructions, from other repositories
understudy qa-engineer.instructions.md
Instructions for erniker/understudy, covering qa engineer — quality assurance specialist instructions, 🎯 recommended model: {{modelqa}}, (use /model in cli or model picker in vs code), identity and expertise.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.