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 Mallikarjun-Roddannavar/playwright-agentic-automation --skill qa-safe-healinggit clone --depth 1 https://github.com/Mallikarjun-Roddannavar/playwright-agentic-automationWrote 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/mallikarjun-roddannavar/playwright-agentic-automation/qa-safe-healing)<a href="https://agentmods.dev/skills/mallikarjun-roddannavar/playwright-agentic-automation/qa-safe-healing"><img src="https://agentmods.dev/badge/skills/mallikarjun-roddannavar/playwright-agentic-automation/qa-safe-healing/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/mallikarjun-roddannavar/playwright-agentic-automation/qa-safe-healing"><img src="https://agentmods.dev/badge/skills/mallikarjun-roddannavar/playwright-agentic-automation/qa-safe-healing.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.00023 | $0.00285 |
| Opus 5 | $0.00012 | $0.00143 |
| Sonnet 5 | $0.00005 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
qa-safe-healing 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 4d 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.
What it actually says
QA Safe Healing
Use this skill for a failed Playwright test, a request to heal a test, or a diagnosis-only QA report. It complements full-stack-incident-analyst; use that skill when source-to-runtime tracing needs a full cross-layer RCA.
- Read
qa/failure-taxonomy.jsonandqa/evidence-schema.json. - Preserve test output, trace/screenshot when available, API/network evidence, source, and relevant product knowledge.
- Explain test intent and supported behavior separately; emit classification, confidence, evidence, root-cause hypothesis, and
testModificationAllowed. - In diagnosis-only mode, change nothing. Missing evidence means
UNKNOWN, not a guess. - Modify only if policy permits it. Never weaken assertions, skip/fixme/delete tests, swallow errors, or force actions.
- Make the smallest repair, run
npm run qa:guardrails, rerun the affected test, and report the exact change and evidence location.
APPLICATION_DEFECT, API_CONTRACT, ENVIRONMENT, and UNKNOWN preserve the failure. LOCATOR_DRIFT permits only a high-confidence locator-only repair. TIMING, TEST_DATA, and ASSERTION_ERROR require review.
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.
- 4d ago First seen · 18 lines · 23 tokens per session scan A 322f587b599b
qa-safe-healing is a skill published in the GitHub repository Mallikarjun-Roddannavar/playwright-agentic-automation (11 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 285 once invoked, about $0.0001 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-09-08.
Other skills, from other repositories
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
qa-expert
Expert-level quality assurance, testing strategies, automation, and QA processes. Use when the user mentions testing, test automation, quality assurance, or Selenium, or when the task involves Testing Types, QA Processes, Test Strategy, or Defect Management.
test-runner
Use this skill when orchestrating agentic end-to-end tests. Resolves target + profile, dispatches the right driver(s) (playwright for web today, peekaboo for macOS (issue #381)), invokes the ux-evaluator agent (opus, read-only) against driver artifacts, reconciles findings with the open issue tracker via…
phoenicurus
Skill "phoenicurus" from markmhendrickson/ateles, covering phoenicurus — qa, identity, agents are the primary users, principals and job.
review
Review code changes, pull requests, patches, or a scoped code area for actionable correctness, security, compatibility, and test risks with file and line evidence. Use for review or audit requests; do not use for general proofreading, feature implementation, or debugging a reported failure when the user wants a fix.
debug
Diagnose a concrete failure, regression, crash, hang, flaky test, or incorrect runtime behavior by reproducing it, testing hypotheses, and identifying the evidence-backed root cause. Use when symptoms or failing output exist; do not use for feature implementation without a failure, general code review, or a conceptual…