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 skills add katalon-labs/true-skills --skill get-startedgit 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/skills/katalon-labs/true-skills/get-started)<a href="https://agentmods.dev/skills/katalon-labs/true-skills/get-started"><img src="https://agentmods.dev/badge/skills/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/skills/katalon-labs/true-skills/get-started"><img src="https://agentmods.dev/badge/skills/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.00145 | $0.00829 |
| Opus 5.5 | $0.00058 | $0.00332 |
| Sonnet 5.5 | $0.00029 | $0.00166 |
| Haiku 4.5 | $0.00015 | $0.00083 |
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 14d 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 — 39 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.
- 14d ago First seen · 39 lines · 145 tokens per session scan A 5cd6b253e689
get-started is a skill published in the GitHub repository katalon-labs/true-skills (10 stars, last pushed 15d ago), licensed MIT. It adds 145 tokens to every session and 829 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 skills, from other repositories
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
data-quality-frameworks
Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
First-Time User Tester
Validate the first-time user experience including onboarding flows, empty states, tutorial completion, progressive disclosure, and initial setup wizards.