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 lfyxhappy/lfcode --skill flaky-test-triagegit clone --depth 1 https://github.com/lfyxhappy/lfcodeWrote 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/lfyxhappy/lfcode/flaky-test-triage)<a href="https://agentmods.dev/skills/lfyxhappy/lfcode/flaky-test-triage"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/flaky-test-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/lfyxhappy/lfcode/flaky-test-triage"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/flaky-test-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.00063 | $0.00403 |
| Opus 5.5 | $0.00025 | $0.00161 |
| Sonnet 5.5 | $0.00013 | $0.00081 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
flaky-test-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.
What it actually says
Flaky Test Triage
Turn an intermittent failure into a bounded causal explanation and a durable repair.
Workflow
- Read repository instructions, the failing test, test history or logs, fixture lifecycle, relevant concurrency settings, and recent changes.
- Record the exact failure signature, frequency, seed, order, platform, runtime version, resource use, and retry behavior. Separate distinct symptoms before treating them as one flake.
- Repeat the narrowest test under controlled variations: isolation versus suite, changed order, fixed seed, constrained parallelism, clean versus warm state, and relevant platform or clock conditions.
- Inspect asynchronous completion, shared state, cleanup, network and filesystem boundaries, random generation, time zones, timers, process lifetime, and test runner configuration.
- Fix the causal synchronization, isolation, data ownership, or lifecycle defect. Add a regression test or deterministic harness only when it proves the repaired condition.
- Rerun the focused test enough to validate the hypothesis, then run the affected suite with its normal concurrency settings.
Boundaries
- Keep triage read-only unless the user asks to modify tests, infrastructure, or product code.
- Do not disable, skip, quarantine, retry indefinitely, lengthen arbitrary timeouts, or add sleeps as a substitute for a root-cause fix.
- Do not call a test flaky without evidence that distinguishes nondeterminism from a deterministic product regression.
- Redact credentials, customer data, and machine-specific sensitive information from logs and reports.
Completion Check
Report the intermittent symptom, reproduction matrix, root cause or bounded hypothesis, repair, repetition evidence, suite result, and residual uncertainty.
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 · 29 lines · 63 tokens per session scan A 2533c32228d0
flaky-test-triage is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 403 once invoked, about $0.0003 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-05.
Other skills, from other repositories
investigate
A structured root-cause investigation method for software bugs. It moves from history and reproduction through tested hypotheses, a focused fix, verification, and a report.
PR babysit (watch & drive to green)
Watch a pull request and delegate fixes until CI is green and reviews are addressed. Requires the GitHub MCP server or gh.
Check work (verify against criteria)
Verify an implementation against acceptance criteria with a reviewer and a tester.
Debug (reproduce -> isolate -> fix)
Systematically diagnose and fix a bug instead of guessing.
Write tests
Add focused, meaningful tests for code — happy path plus the edge cases that matter.
bug-fix
A structured bug-fixing workflow that takes a problem from reproduction and evidence-based cause finding through approval, implementation, testing, and cleanup.