What is true-skills test-maintenance.md?

A set of instructions for maintaining a Katalon regression suite over time. A regression suite is a group of tests rerun to check that existing behavior still works after changes.

Assessing change impact, diagnosing unstable or outdated cases, repairing case content, and refreshing the list of coverage gaps.

It uses failure and stability signals to identify cases that need repair, movement, duplication, or retirement, while distinguishing case edits from deeper script or object repairs.

How katalon-labs/true-skills configures Kiro

Reuse

Borrowing it

Nothing to install: this file belongs to katalon-labs/true-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/katalon-labs/true-skills/main/.kiro/steering/test-maintenance.md

Clone the repo

git clone --depth 1 https://github.com/katalon-labs/true-skills

Made for: Kiro.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/katalon-labs/true-skills/test-maintenance/github.svg)](https://agentmods.dev/instructions/katalon-labs/true-skills/test-maintenance)

Your own site

<a href="https://agentmods.dev/instructions/katalon-labs/true-skills/test-maintenance"><img src="https://agentmods.dev/badge/instructions/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/katalon-labs/true-skills/test-maintenance"><img src="https://agentmods.dev/badge/instructions/katalon-labs/true-skills/test-maintenance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,192 This file is loaded in full into every session.

When invoked 1,192 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.01192	$0.01192
Opus 5.5	$0.00477	$0.00477
Sonnet 5.5	$0.00238	$0.00238
Haiku 4.5	$0.00119	$0.00119

Measured 1mo ago against content hash af3bac389d7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

true-skills test-maintenance.md 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 1mo 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.

.kiro/steering/test-maintenance.md · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 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_data for flakiness trend; find_test_results + read_execution for 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 via move_test_case; branch a variant via duplicate_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 (MCP-legal edits only). Pass all intended updates in one update_test_case call. Do not claim to have self-healed locators/objects — that is Studio.
Validate. Re-run through execute-test and confirm via find_test_results / read_execution.
Feed back. Emit the refreshed coverage gap list to test-plan so maintenance closes the loop instead of dead-ending.

Read the full file on GitHub · 107 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.

1mo ago First seen · 107 lines · 1,192 tokens per session scan A af3bac389d7e

Subscribe to this mod's changes

true-skills test-maintenance.md is an instructions file published in the GitHub repository katalon-labs/true-skills (10 stars, last pushed 4d ago), licensed MIT. It adds 1,192 tokens to every session, about $0.0048 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-09-08.

Claude Code Testing agent-skills agentic-ai ai-testing cursor github-copilot

understudy qa-engineer.instructions.md

Instructions for erniker/understudy, covering qa engineer — quality assurance specialist instructions, 🎯 recommended model: {{modelqa}}, (use /model in cli or model picker in vs code), identity and expertise.

erniker/understudy · 1,600 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

true-skills: Instructions file for Kiro