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 test-maintenancegit 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/test-maintenance)<a href="https://agentmods.dev/skills/katalon-labs/true-skills/test-maintenance"><img src="https://agentmods.dev/badge/skills/katalon-labs/true-skills/test-maintenance/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/test-maintenance"><img src="https://agentmods.dev/badge/skills/katalon-labs/true-skills/test-maintenance.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.00135 | $0.00852 |
| Opus 5 | $0.00068 | $0.00426 |
| Sonnet 5 | $0.00027 | $0.00170 |
| Haiku 4.5 | $0.00014 | $0.00085 |
Grade A, and why
test-maintenance 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 12d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Katalon Test Maintenance
Use this skill for the maintenance stage: keep the regression suite healthy over time and feed learning back to the plan. It consumes failure/stability signals and produces repairs plus a refreshed coverage gap list.
Availability Boundary
- Available via MCP: change/impact signals (
fetch_test_stability_data,find_test_results,read_execution), and case-level repair (update_test_case,move_test_case,duplicate_test_case). - Not directly available: Self-healing tests, Time Capsule, Studio Tracer, object refactoring, and StudioAssist Agent-mode edits are Studio-desktop features. TrueTest regeneration from live journeys is a TrueTest surface. Narrate these; MCP repairs are case-level content edits, not object/script self-healing.
Maintenance Workflow
+---------------------+ +----------------------+ +----------------------+
| Detect change impact| --> | Diagnose: repair vs | --> | Repair case assets |
| stability + history | | regenerate vs retire | | update/move/dup |
+---------------------+ +----------------------+ +----------------------+
|
v
+----------------------+
| Validate + feed back |
| to plan (gap list) |
+----------------------+
Steps and tool rules
- Detect impact.
fetch_test_stability_datafor flakiness trend;find_test_results+read_executionfor what changed across recent runs. Build the list of broken / flaky / degraded cases. - Diagnose each. Decide per case:
- Repair — the case is salvageable: fix data, steps, or expected result via
update_test_case; reorganize viamove_test_case; branch a variant viaduplicate_test_case. - Regenerate — behavior changed enough that the case should be re-derived (TrueTest regeneration / re-author) -> hand to
create-test-cases; narrate the TrueTest boundary. - Retire — behavior removed: unlink/retire (prefer update/flag over unreliable
delete_test_case); get approval.
- Repair — the case is salvageable: fix data, steps, or expected result via
- Repair (MCP-legal edits only). Pass all intended updates in one
update_test_casecall. Do not claim to have self-healed locators/objects — that is Studio. - Validate. Re-run through
execute-testand confirm viafind_test_results/read_execution. - Feed back. Emit the refreshed coverage gap list to
test-planso maintenance closes the loop instead of dead-ending.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 55 lines · 135 tokens per session scan A 7b3ad254c242
test-maintenance is a skill published in the GitHub repository katalon-labs/true-skills (8 stars, last pushed 3d ago), licensed MIT. It adds 135 tokens to every session and 852 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 skills, from other repositories
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
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.
First-Time User Tester
Validate the first-time user experience including onboarding flows, empty states, tutorial completion, progressive disclosure, and initial setup wizards.
Angry User Simulator
Simulate aggressive user behavior patterns including rapid clicking, random navigation, form abuse, tab spamming, and unexpected interaction sequences to find UI resilience issues.
Console Error Hunter
Systematically detect, capture, and categorize browser console errors, warnings, and unhandled exceptions during automated test execution.
Appium Mobile Testing
Mobile application testing skill using Appium for iOS and Android, covering device capabilities, selectors, gestures, and cross-platform testing strategies.