true-skills: Instructions file for Kiro

.kiro/steering/execute-test.md

true-skills execute-test.md is an instructions file for Kiro from katalon-labs/true-skills. It costs 1,822 tokens per session, scanned A, original, MIT.

A workflow for running selected Katalon test cases or suites and reporting their outcomes. A test suite is a group of test cases run together for a shared purpose.

In plain words
What is it for?
Use it to inspect available application environments, create manual runs, start AI-assisted runs, schedule automated suite runs, and read execution results.
Why use it?
It prevents runs from starting with the wrong project, repository, environment, or execution method. It also states when a Katalon connection cannot inspect the live application or guarantee that an AI run will finish.

Instructions file for Kiro

Written for Kiro: installed under .kiro/.

This is katalon-labs/true-skills's own configuration. It tells Kiro how to work on true-skills itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything true-skills configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/katalon-labs/true-skills/main/.kiro/steering/execute-test.md
Clone the repo
git clone --depth 1 https://github.com/katalon-labs/true-skills

Made for: Kiro.

Wrote 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.

agentmods badge for true-skills execute-test.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/katalon-labs/true-skills/execute-test/github.svg)](https://agentmods.dev/instructions/katalon-labs/true-skills/execute-test)
Your own site
<a href="https://agentmods.dev/instructions/katalon-labs/true-skills/execute-test"><img src="https://agentmods.dev/badge/instructions/katalon-labs/true-skills/execute-test/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.

agentmods 80×15 button for true-skills execute-test.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/katalon-labs/true-skills/execute-test"><img src="https://agentmods.dev/badge/instructions/katalon-labs/true-skills/execute-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,822 This file is loaded in full into every session.
When invoked 1,822 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01822 $0.01822
Opus 5.5 $0.00729 $0.00729
Sonnet 5.5 $0.00364 $0.00364
Haiku 4.5 $0.00182 $0.00182

Measured 1mo ago against content hash 68861b1383f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

true-skills execute-test.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.

.kiro/steering/execute-test.md · 201 lines

How it starts

The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Katalon Execute Test

Use this skill for running already-selected Katalon test cases or suites and reporting execution outcomes. Keep the larger true-platform-testing skill as the end-to-end orchestrator; this skill is the focused execution workflow.

Availability Boundary

State the execution boundary before running:

  • Available: read AUT environments, create manual test runs, start Run with AI, poll AI sessions, schedule automated suite runs, and read execution/test results.
  • Not directly available: guarantee AI completion, inspect the live AUT UI through Katalon MCP, or run manual test cases through the automated scheduler.
  • Use Browser/Playwright only when AUT exploration or visual verification outside Katalon MCP is needed.

Read references/capability-boundaries.md when capability scope is unclear.

Resolve Context First

Before creating or scheduling any run:

  1. Call list_projects.
  2. Call list_repositories.
  3. Resolve the repository/Test Project from the user's wording or unique available repository.

Ask only when multiple equally valid repositories remain, required credentials are missing, or the next action is destructive.

Choose Execution Type

Use manual execution when:

  • The user provides manual test cases.
  • The user asks for Run with AI.
  • The test cases were just created in Katalon.
  • The input is a manual suite.

Use automated execution only when the input is an automated suite or suite collection.

If the user only says "run tests" and the type cannot be inferred, ask whether they want manual or automated execution.

Manual Run With AI

Always follow this order:

  1. Call read_auts immediately before create_manual_test_run.
  2. Resolve the manual cases or suites.
  3. If a suite is provided, call read_test_suite before creating the run.
  4. If individual cases are provided, call read_test_case for unclear or risky inputs.
  5. Create the manual run with create_manual_test_run.
  6. Start Run with AI automatically with create_manual_ai_session unless the user explicitly says not to run AI.
  7. Poll read_manual_ai_session until all items leave TODO/IN_TESTING, or the platform returns an external timeout/error.
  8. Read available execution/test result details before responding.

Read the full file on GitHub · 201 lines

Changes

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.

  1. 1mo ago First seen · 201 lines · 1,822 tokens per session scan A 68861b1383f8

Subscribe to this mod's changes

true-skills execute-test.md is an instructions file published in the GitHub repository katalon-labs/true-skills (10 stars, last pushed 4d ago), licensed MIT. It adds 1,822 tokens to every session, about $0.0073 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.

Related

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.

erniker/understudy · 1,600 tokens

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,581 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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.

deepseek-ai/deepseek-harness · 4,261 tokens