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/get-started)<a href="https://agentmods.dev/rules/katalon-labs/true-skills/get-started"><img src="https://agentmods.dev/badge/rules/katalon-labs/true-skills/get-started/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/rules/katalon-labs/true-skills/get-started"><img src="https://agentmods.dev/badge/rules/katalon-labs/true-skills/get-started.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.00141 | $0.00847 |
| Opus 5.5 | $0.00056 | $0.00339 |
| Sonnet 5.5 | $0.00028 | $0.00169 |
| Haiku 4.5 | $0.00014 | $0.00085 |
Grade A, and why
get-started 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 13d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Katalon Get Started
Run this once after the Katalon connection is installed. The goal is a stored default project and a first useful view in under a minute, with at most two questions.
Boundary
- Reads only, plus one settings save. Nothing in the user's workspace changes.
- Never ask for a password, API key or token. Sign-in happens in the client's own Katalon sign-in screen.
- Never repeat the user's email address back to them.
- Some tools below exist only on clients that render Katalon cards and store settings (
katalon_profile,settings_update,katalon_home). When a tool is not listed in this session, skip that step as described and carry on.
Steps
- Who is signed in. Call
katalon_profile. Greet in one line with the organization and account name fromnickname, for example "You are connected to Katalon as Katalon Demo / Demo Shop." Ifkatalon_profileis not listed, skip the greeting. If the call says the user is not signed in, tell them to sign in to Katalon from the connection prompt and stop. - Default project (question 1). Call
list_projects. If there is exactly one project, use it and do not ask. Otherwise ask one question offering the three most recently used projects by name, plus "another project". If the user names another project, match it by name from the same list. - Repository and Run with AI target (question 2, only if needed). Call
list_repositoriesandread_autsfor the chosen project.- One repository and at most one AUT environment: use them and do not ask.
- More than one of either: ask one combined question, for example "Which repository and which environment should Run with AI use by default?", listing at most three options for each.
- No AUT environment: leave the Run with AI target unset and say Run with AI asks for it on first use.
- Save. Call
settings_updatewith{"set": {"default_project_id": ..., "default_repository_id": ..., "default_aut_environment_id": ...}}, leaving out any value that was not chosen. Ifsettings_updateis not listed, say which project and repository this conversation will use and skip saving. - First view. Call
katalon_homeso the user lands on their runs, uncovered requirements and release status. Where cards do not render, orkatalon_homeis not listed, end with these three starter prompts instead:- "Which requirements in my next release have no tests?"
- "Why did my latest test run fail?"
- "Is my next release ready to ship?"
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.
- 13d ago First seen · 41 lines · 141 tokens per session scan A be9e78ae6001
get-started is a cursor rule published in the GitHub repository katalon-labs/true-skills (10 stars, last pushed 14d ago), licensed MIT. It adds 141 tokens to every session and 847 once invoked, about $0.0006 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-10-03.
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.
vibe-test
How to use the vibe-test MCP server for browser testing.
fusebase-flow-validation
Fusebase Flow validation/verification phase rules. Use when running gate checks, reviewing diffs, or verifying smoke prompts.
minimax-m3-status-verification
MiniMax M3 status and verification contract: exact claim labels, proof matching, multimodal-grounded visual claims, and evidence-first closeouts.
testing
Optional Spring Boot example-pack testing rules. Apply only when editing an adopted project or spring-boot profile output.
fusebase-flow-implementation
Fusebase Flow implementation phase rules. Use when editing source code per a locked spec.