Borrowing it
Nothing to install: this file belongs to kint4/autoframe. 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/kint4/autoframe/main/.claude/skills/flake-check/SKILL.mdgit clone --depth 1 https://github.com/kint4/autoframeWrote 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/kint4/autoframe/flake-check)<a href="https://agentmods.dev/skills/kint4/autoframe/flake-check"><img src="https://agentmods.dev/badge/skills/kint4/autoframe/flake-check/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/kint4/autoframe/flake-check"><img src="https://agentmods.dev/badge/skills/kint4/autoframe/flake-check.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.00040 | $0.00445 |
| Opus 5.5 | $0.00016 | $0.00178 |
| Sonnet 5.5 | $0.00008 | $0.00089 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
flake-check 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 2mo 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
/flake-check — Diagnose Flaky Tests
Type: Functional Description: Analyzes failing or unstable tests and diagnoses whether the cause is a flaky selector, a timing/race issue, test data, or a real product bug — then proposes a fix.
Input Format
Any of:
- A path to a spec file or test name
- A pasted failure log / stack trace
- A description of the intermittent behavior
Output Format
A diagnosis report containing:
- Classification: flaky selector / timing issue / test data / environment / real bug
- Evidence: the specific lines or signals that point to the cause
- Recommended fix: concrete code change following Autoframe conventions
- Confidence: high / medium / low
Step-by-Step Instructions
- Read the relevant spec and its Page Object(s).
- Inspect the failure signal (log, trace, or description).
- Check for the common flake causes, in order:
- Selectors: brittle CSS /
page.$()/ nth-based locators → recommend semanticgetByRole/getByLabel. - Timing: hard waits (
waitForTimeout), missing auto-waiting assertions, race conditions → recommend web-firstexpectassertions and removing fixed sleeps. - Test data: shared/mutable state, ordering dependencies → recommend factories and isolation.
- Environment: network, auth token expiry, base URL.
- Real bug: behavior is genuinely wrong → recommend
/bug-from-failure.
- Selectors: brittle CSS /
- State the classification with evidence and a confidence level.
- Propose the fix as a concrete diff that follows POM and spec conventions.
- If it's a real bug, route the user to
/bug-from-failure.
Rules
- Prefer fixing the root cause over adding retries.
- Never recommend
waitForTimeoutas a fix. - Always classify before proposing a change.
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.
- 2mo ago First seen · 47 lines · 0 tokens per session scan A 2398c0532238
flake-check is a skill published in the GitHub repository kint4/autoframe (8 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 445 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-08-31.
Other skills, from other repositories
k6-load-testing
Comprehensive k6 load testing skill for API, browser, and scalability testing. Write realistic load scenarios, analyze results, and integrate with CI/CD.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; run or list flows…
aif-web-testing
Test web apps with Playwright, Vitest and k6: E2E, unit, integration, load, security, visual and a11y.
agent-qa-authoring
Use when creating, editing, validating, or running agent-qa tests, suites, or hooks. Prefer agent-qa MCP tools, enforce canonical agent-qa IDs, and use the bundled schema reference to avoid hallucinated config keys or YAML fields.
agent-qa-result-triage
Use when investigating failed agent-qa runs, inspecting artifacts, classifying failures, or comparing recent runs. Prefer agent-qa MCP run/artifact tools and produce evidence-backed triage.