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 agentmods add rules/katalon-labs/true-skills/execute-testgit 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/execute-test)<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>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 | $0.00136 | $0.01960 |
| Opus 5 | $0.00068 | $0.00980 |
| Sonnet 5 | $0.00027 | $0.00392 |
| Haiku 4.5 | $0.00014 | $0.00196 |
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.
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:
- Call
list_projects. - Call
list_repositories. - 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:
- Call
read_autsimmediately beforecreate_manual_test_run. - Resolve the manual cases or suites.
- If a suite is provided, call
read_test_suitebefore creating the run. - If individual cases are provided, call
read_test_casefor unclear or risky inputs. - Create the manual run with
create_manual_test_run. - Start Run with AI automatically with
create_manual_ai_sessionunless the user explicitly says not to run AI. - Poll
read_manual_ai_sessionuntil all items leave TODO/IN_TESTING, or the platform returns an external timeout/error. - Read available execution/test result details before responding.
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.
- 3d ago First seen · 202 lines · 136 tokens per session scan A 326adf07170e
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.
Other cursor rules, from other repositories
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
language-agnostic-patterns
Language-agnostic programming patterns: SOLID, design patterns, clean code, and architecture. Load when refactoring, designing abstractions, or reviewing structure — not for everyday syntax.
cursor-tools-mastery
Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.
cursor-agent-orchestration
Cursor 3.7 orchestration guide: when to plan, when to delegate, nested subagents, multi-environment handoffs, /best-of-n, and Await for long-running branches.
fable5-reasoning
Fable 5 reasoning protocols: task interpretation, risk-first decomposition, approach selection, interleaved thinking, hypothesis ledgers, premortems, calibration, and the stuck-strategy ladder. Load for complex, ambiguous, or long-horizon tasks, for debugging strategy, or whenever progress stalls.
cursor-mcp-optimization
Cursor 3.7 MCP optimization: browser Design Mode, canvases, Figma, Cloudflare tools, MCP Apps structured content, and direct action patterns.