execute-test

execute-test is a cursor rule for Cursor from katalon-labs/true-skills. It costs 136 tokens per session (1,960 once invoked), scanned A, original, MIT.

A test-execution workflow for running existing Katalon test cases, manual test lists, suites, or execution requests in Katalon True Platform. It can also start Katalon's AI-assisted runs and read their results.

In plain words
What is it for?
Use it to resolve the correct project and repository, create manual runs, schedule automated suite runs, start Run with AI, monitor sessions, and read execution results.
Why use it?
It provides a consistent way to start scheduled or manual runs and track their outcomes without confusing test selection with test creation.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/katalon-labs/true-skills/execute-test
Clone the repo
git clone --depth 1 https://github.com/katalon-labs/true-skills

Made for: Cursor.

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 execute-test

README.md
[![agentmods](https://agentmods.dev/badge/rules/katalon-labs/true-skills/execute-test.svg)](https://agentmods.dev/rules/katalon-labs/true-skills/execute-test)
Your own site
<a href="https://agentmods.dev/rules/katalon-labs/true-skills/execute-test"><img src="https://agentmods.dev/badge/rules/katalon-labs/true-skills/execute-test.svg" alt="Measured on agentmods" height="20"></a>
Per session 136 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,960 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00136 $0.01960
Opus 5 $0.00068 $0.00980
Sonnet 5 $0.00027 $0.00392
Haiku 4.5 $0.00014 $0.00196

Measured 3d ago against content hash 326adf07170e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

execute-test 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 3d 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.

.cursor/rules/execute-test.mdc · 202 lines

How it starts

The opening of the file, as written. The whole thing — 202 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 · 202 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. 3d ago First seen · 202 lines · 136 tokens per session scan A 326adf07170e

Subscribe to this mod's changes

execute-test is a cursor rule published in the GitHub repository katalon-labs/true-skills (7 stars, last pushed 8d ago), licensed MIT. It adds 136 tokens to every session and 1,960 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.

Related

Other cursor rules, from other repositories