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 DamingDong/opencode-skills-hub --skill flaky-test-detectorgit clone --depth 1 https://github.com/DamingDong/opencode-skills-hubWrote 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/damingdong/opencode-skills-hub/flaky-test-detector)<a href="https://agentmods.dev/skills/damingdong/opencode-skills-hub/flaky-test-detector"><img src="https://agentmods.dev/badge/skills/damingdong/opencode-skills-hub/flaky-test-detector/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/damingdong/opencode-skills-hub/flaky-test-detector"><img src="https://agentmods.dev/badge/skills/damingdong/opencode-skills-hub/flaky-test-detector.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.00066 | $0.00432 |
| Opus 5 | $0.00033 | $0.00216 |
| Sonnet 5 | $0.00013 | $0.00086 |
| Haiku 4.5 | $0.00007 | $0.00043 |
Grade A, and why
flaky-test-detector 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 6d 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 Detector
Overview
This skill provides automated assistance for flaky test detector tasks within the Test Automation domain.
When to Use
This skill activates automatically when you:
- Mention "flaky test detector" in your request
- Ask about flaky test detector patterns or best practices
- Need help with test automation skills covering unit testing, integration testing, mocking, and test framework configuration.
Instructions
- Provides step-by-step guidance for flaky test detector
- Follows industry best practices and patterns
- Generates production-ready code and configurations
- Validates outputs against common standards
Examples
Example: Basic Usage Request: "Help me with flaky test detector" Result: Provides step-by-step guidance and generates appropriate configurations
Prerequisites
- Relevant development environment configured
- Access to necessary tools and services
- Basic understanding of test automation concepts
Output
- Generated configurations and code
- Best practice recommendations
- Validation results
Error Handling
| Error | Cause | Solution |
|---|---|---|
| Configuration invalid | Missing required fields | Check documentation for required parameters |
| Tool not found | Dependency not installed | Install required tools per prerequisites |
| Permission denied | Insufficient access | Verify credentials and permissions |
Resources
- Official documentation for related tools
- Best practices guides
- Community examples and tutorials
Related Skills
Part of the Test Automation skill category. Tags: testing, jest, pytest, mocking, tdd
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.
- 6d ago First seen · 73 lines · 66 tokens per session scan A c894a452b667
flaky-test-detector is a skill published in the GitHub repository DamingDong/opencode-skills-hub (11 stars, last pushed 7mo ago), licensed MIT. It adds 66 tokens to every session and 432 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.