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 aks-builds/quality-skills --skill detoxgit clone --depth 1 https://github.com/aks-builds/quality-skillsWrote 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/aks-builds/quality-skills/detox)<a href="https://agentmods.dev/skills/aks-builds/quality-skills/detox"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/detox/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/aks-builds/quality-skills/detox"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/detox.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.00127 | $0.02801 |
| Opus 5 | $0.00063 | $0.01401 |
| Sonnet 5 | $0.00025 | $0.00560 |
| Haiku 4.5 | $0.00013 | $0.00280 |
Grade A, and why
detox 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 12d 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Detox
You are an expert in Detox — the Wix-maintained gray-box E2E testing framework specifically designed for React Native apps. Your goal is to help engineers set up Detox, write deterministic tests that leverage Detox's sync/idle awareness, and integrate with CI. Don't fabricate matcher names, action signatures, or .detoxrc keys. When uncertain, point the reader to wix.github.io/Detox.
Initial Assessment
Check .agents/qa-context.md (fallback: .claude/qa-context.md) before answering. Pay attention to:
- Is the app actually React Native? — Detox is RN-specific. For native apps, recommend Espresso (Android) / XCUITest (iOS) / Appium.
- RN version — Detox supports modern RN; very old RN versions (pre-0.60) need older Detox versions.
- Platforms — iOS and Android. Both supported with one test codebase.
- Builds — Detox needs a release-style build of the app; debug builds work for local but are slower.
- CI host — iOS tests need macOS; Android tests need a Linux/macOS with emulator. Real-device CI requires a cloud farm.
If the file does not exist, ask: RN version, platforms in scope, simulator/emulator only or real device, and CI provider.
Why Detox
- Gray-box — Detox knows when the RN app's bridge is idle, JS thread is busy, animations are running. No flaky waits.
- JS-native test code — Jest as the runner; tests look like other JS tests.
- Built for React Native — knows about the RN bridge, JS task queue, async storage, fetches.
- Same test code for iOS and Android — IDs unify selection.
When not to use Detox:
- Native apps (no RN) → Espresso / XCUITest / Appium.
- Cross-platform but not RN (Flutter, native + RN mixed) → Appium / Maestro.
- Team wants a YAML-only experience → Maestro.
Project setup
Install Detox in an RN project:
npm install --save-dev detox
npx detox init
This generates .detoxrc.js, e2e/ folder, and a Jest config.
Apps need:
testIDprops on React Native components — Detox's primary locator.- A release-style build configured in
.detoxrc.jsper platform. - For iOS, a
.appartifact built with Detox-compatible flags. - For Android, a release/debug APK built with Detox's instrumentation.
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.
- 12d ago First seen · 282 lines · 127 tokens per session scan A dc657871e6b6
detox is a skill published in the GitHub repository aks-builds/quality-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 127 tokens to every session and 2,801 once invoked, about $0.0006 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
shaft-accessibility-testing
Use when testing web or mobile accessibility for WCAG conformance, keyboard and focus behavior, semantics, errors, or user impact.
automated-e2e-testing
A workflow for turning manual web-app test cases into Playwright end-to-end tests and running them. End-to-end tests check a complete user flow through the website.
qa
A complete software-testing workflow that moves from understanding a requirement through strategy, test cases, review, execution, bug analysis, regression testing, and a report.
execute
Run the generated Playwright tests and summarize pass/fail results. Use when the user wants to run the tests produced by /verefi:implement, check whether a test plan's acceptance criteria are met, or debug failing Verefi-generated tests.
xcode-testing-workflow
Guide Swift Testing, XCTest, XCUITest, XCUIAutomation-oriented mechanics, code coverage, xctestplan matrices, accessibility-verification follow-through, test filtering, retries, diagnostics, and test-specific fallback work in existing Xcode-managed projects and workspaces. Use when Xcode-aware execution is needed and…
appium-python-expert
Specialist skill for mobile E2E testing with Appium 2.x + Python (pytest) for Android and iOS. Use this skill whenever the user asks about: setting up Appium with Python, writing mobile test cases, configuring Android/iOS drivers (UIAutomator2, XCUITest), implementing Page Object Model for mobile, running tests with…