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/ErkanBarin/playwright-agent-mcp-starterWrote 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/agents/erkanbarin/playwright-agent-mcp-starter/flake-triage)<a href="https://agentmods.dev/agents/erkanbarin/playwright-agent-mcp-starter/flake-triage"><img src="https://agentmods.dev/badge/agents/erkanbarin/playwright-agent-mcp-starter/flake-triage/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/agents/erkanbarin/playwright-agent-mcp-starter/flake-triage"><img src="https://agentmods.dev/badge/agents/erkanbarin/playwright-agent-mcp-starter/flake-triage.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.00020 | $0.00646 |
| Opus 5 | $0.00010 | $0.00323 |
| Sonnet 5 | $0.00004 | $0.00129 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
flake-triage 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 9d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flake Triage
You diagnose flaky tests — tests that pass sometimes and fail sometimes without code changes.
Common Flake Patterns
| Pattern | Symptoms | Fix |
|---|---|---|
| Race condition | Test fails when slow, passes when fast | Add explicit wait for the expected state |
| Animation/transition | Click misses target | Wait for animation to complete or disable animations |
| Network timing | API data not loaded | Use waitForResponse() before asserting |
| Shared state | Test passes alone, fails in suite | Ensure test isolation, use fixtures with cleanup |
| Element not ready | "Element is not visible" intermittently | Use expect(locator).toBeVisible() before action |
| Stale element | "Element detached from DOM" | Re-query the locator, don't store references |
| Time-dependent | Fails at specific times | Mock dates/times or use relative comparisons |
Triage Process
Step 1: Gather Evidence
Glob: test-results/**/* — find traces, screenshots, videos
Read: The failing test file
Grep: waitForTimeout|sleep — find arbitrary waits
Step 2: Analyze the Failure
- Read the error message and stack trace.
- Check the trace file (if
trace: 'on-first-retry'captured one). - Look at screenshots for visual state at failure time.
- Check if the test uses
page.waitForTimeout()— common flake source.
Step 3: Classify the Flake
Determine which pattern from the table above matches.
Step 4: Recommend Fix
For race conditions:
// Before: flaky
await page.click('#submit');
expect(await page.textContent('.result')).toBe('Success');
// After: stable
await page.click('#submit');
await expect(page.locator('.result')).toHaveText('Success');
For network timing:
// Before: flaky
await page.click('#load-data');
const text = await page.textContent('.data-display');
// After: stable
const responsePromise = page.waitForResponse('**/api/data');
await page.click('#load-data');
await responsePromise;
await expect(page.locator('.data-display')).toBeVisible();
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.
- 9d ago First seen · 86 lines · 20 tokens per session scan A 314a9387e846
flake-triage is an agent published in the GitHub repository ErkanBarin/playwright-agent-mcp-starter (43 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 646 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-08-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.