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 agentmods add skills/theshadow27/mcp-cli/flaky-testsnpx skills add theshadow27/mcp-cli --skill flaky-testsgit clone --depth 1 https://github.com/theshadow27/mcp-cliWrote 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/theshadow27/mcp-cli/flaky-tests)<a href="https://agentmods.dev/skills/theshadow27/mcp-cli/flaky-tests"><img src="https://agentmods.dev/badge/skills/theshadow27/mcp-cli/flaky-tests.svg" alt="Measured on agentmods" 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 | $0.00087 | $0.00489 |
| Opus 5 | $0.00044 | $0.00244 |
| Sonnet 5 | $0.00017 | $0.00098 |
| Haiku 4.5 | $0.00009 | $0.00049 |
Grade A, and why
flaky-tests 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 5d 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 Mining
Scan session transcripts to identify tests that fail across multiple sessions — the signature of true flakiness vs one-time breakage.
How it works
bun run .claude/skills/flaky-tests/mine-flaky-tests.ts --since 2026-03-10
Always pass --since with a recent date (e.g. the start of the last sprint) to
avoid counting failures from before known fixes landed. Without it, the script
scans every session file ever created and will report stale hits.
The script:
- Reads JSONL session files for the current project (filtered by
--sinceif given) - Extracts tool result content (Bash output from test runs)
- Matches bun test failure patterns (
✗,FAIL,expect(...).toEqualmismatches) - Extracts test file name and test description from failure context
- Groups by (file, test) and counts distinct sessions
- Reports sorted by session count — tests appearing in 2+ sessions are truly flaky
Interpreting results
- 3+ sessions: High-confidence flaky. File an issue immediately.
- 2 sessions: Likely flaky. Worth investigating — could be a real regression that got fixed, or a timing-dependent test.
- 1 session, multiple occurrences: Suggests retry loops hit the same failure. May indicate a module-level setup problem rather than test-level flakiness.
After running
- Compare results against existing flaky test issues (
gh issue list --label bug --search "flaky") - File new issues for any newly discovered flaky tests with reproduction data
- Note patterns: are flaky tests concentrated in one file? One subsystem? Filesystem watchers and timing assertions are the usual suspects.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 49 lines · 87 tokens per session scan A 47416df00c1b
flaky-tests is a skill published in the GitHub repository theshadow27/mcp-cli (2 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 489 once invoked, about $0.0004 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…