Borrowing it
Nothing to install: this file belongs to standardbeagle/agnt. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/standardbeagle/agnt/main/.claude/skills/flake-triage/SKILL.mdgit clone --depth 1 https://github.com/standardbeagle/agntWrote 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/standardbeagle/agnt/flake-triage)<a href="https://agentmods.dev/skills/standardbeagle/agnt/flake-triage"><img src="https://agentmods.dev/badge/skills/standardbeagle/agnt/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/skills/standardbeagle/agnt/flake-triage"><img src="https://agentmods.dev/badge/skills/standardbeagle/agnt/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.00043 | $0.00804 |
| Opus 5.5 | $0.00017 | $0.00322 |
| Sonnet 5.5 | $0.00009 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00080 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flake triage
Classify the failure before touching code or deadlines. Most "flakes" in this repo are harness artifacts or data-loss races, not scheduler load.
0. Read what already ran
Read .tman/<alias>.fail.log (e.g. .tman/test.fail.log) at the repo root. Do not rerun the whole suite to find the failure.
1. Where did it fail?
| Signal | Class | Next step |
|---|---|---|
Failed under parallel go test ./... only |
Cross-package port/socket contention | Rerun under -p 1. Green → harness artifact, not a product bug. |
Fails at 0.00s: bootstrap failed, daemon already running, address already in use |
Shared global resource (socket, port, lock file) falling through to a production default | Reproduce with two concurrent test binaries. -p 1 and isolation both hide it. Fix the helper's hermetic default; never widen a deadline. |
| Empty or missing result for the full deadline | Data-loss race (e.g. fd closed before reader drained) | Add a completion barrier, then lower the deadline. |
| Late result, ordering/count assertion off | Wall-clock premise | Rewrite the assertion against recorded timestamps (testing-timing-assertion-flakes.md). |
cmd/agnt red on a task that never touched it |
Known strays: cmd/agnt/AGENTS.md written by a spawned binary, port 5173 contention |
Delete the stray, retry once. |
| Real-Chrome step stalls | Injection bug or renderer starvation | Step 3. |
2. Reproduce the real trigger
- Isolate and intensify the suspected test: tight loop (
-count=N -run '^Name$') plus induced CPU load (stress). - A flake that needs sibling test binaries never reproduces in isolation. Test the condition that actually differs.
- Validate one
go testat a time; concurrent runs pollute each other. - Verify a fix under the same induced load that reproduced it. One clean run proves nothing.
- Spawned-binary tests that only misbehave with a controlling terminal: run under
script -qec '<go test …>' /dev/null. A TTY-less run can skip and give a false clean.
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 · 48 lines · 43 tokens per session scan A d683f22a68e4
flake-triage is a skill published in the GitHub repository standardbeagle/agnt (22 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 804 once invoked, about $0.0002 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-29.
Other skills, from other repositories
browser-test-self-healing
Build an AgentWorks workflow that diagnoses a browser-test failure, proposes a test-only repair, verifies it in isolation, obtains the configured review, and updates canonical tests and application knowledge. Use for stale or flaky browser automation, not product defects.
flaky-test-detection-stabilization
Build AgentWorks browser-test flake detection and reviewed stabilization using repeated isolated attempts and evidence comparison. Use when identical test inputs produce inconsistent outcomes.
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…
pinchtab-dev
Develop and contribute to the PinchTab project. Use when working on PinchTab source code, adding features, fixing bugs, running tests, or preparing PRs. Triggers on "work on pinchtab", "pinchtab development", "contribute to pinchtab", "fix pinchtab bug", "add pinchtab feature".
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
debugging-failures
Diagnose a failing Ginkgo suite as an agent — always run with --json-report into a predictable temp/gitignored location, read the terminal verdict line, then use jq to extract structured failure details (name, message, file:line, panic value, captured logs). Covers the panicked-vs-failed trap, panic locations pointing…