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 SHGrowth/om-superpowers --skill om-integration-testsgit clone --depth 1 https://github.com/SHGrowth/om-superpowersWrote 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/shgrowth/om-superpowers/om-integration-tests)<a href="https://agentmods.dev/skills/shgrowth/om-superpowers/om-integration-tests"><img src="https://agentmods.dev/badge/skills/shgrowth/om-superpowers/om-integration-tests.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 15 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 190 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 196 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 306 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 309 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 312 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00057 | $0.03592 |
| Opus 5 | $0.00028 | $0.01796 |
| Sonnet 5 | $0.00011 | $0.00718 |
| Haiku 4.5 | $0.00006 | $0.00359 |
Grade A, and why
om-integration-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 8d 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Tests Skill
This skill generates executable Playwright tests in module-local __integration__ directories (for example packages/core/src/modules/sales/__integration__/TC-SALES-*.spec.ts) by exploring the running application. It also covers running existing integration tests after feature/bug implementation and reporting failures with artifact-based diagnosis. It optionally produces a markdown scenario (.ai/qa/scenarios/TC-*.md) for documentation — the scenario is not required.
Quick Reference
| Action | Command |
|---|---|
| Run all tests | yarn test:integration |
| Run single test | npx playwright test --config .ai/qa/tests/playwright.config.ts <path> |
| Run in ephemeral containers | yarn test:integration:ephemeral |
| Run interactive ephemeral mode | yarn test:integration:ephemeral:interactive |
| Start ephemeral app only (for MCP exploration, tests development, and debugging) | yarn test:integration:ephemeral:start |
| Run standalone create-app integration parity from monorepo | yarn test:create-app:integration |
| View report | yarn test:integration:report |
| Test files location | <module>/__integration__/TC-XXX.spec.ts (legacy .ai/qa/tests still supported) |
| Scenario sources (optional) | .ai/qa/scenarios/TC-XXX-*.md |
| Reusable env state file | .ai/qa/ephemeral-env.json |
Runtime Policy
Default QA runtime policy:
- Keep global settings in
.ai/qa/tests/playwright.config.ts:timeout: 10_000expect.timeout: 10_000retries: 1
- Do not add per-test timeout or retry overrides in
.spec.tsfiles (test.setTimeout,test.describe.configure({ retries }),test.retry).
Debug/development policy (fail fast while authoring/fixing tests):
- Override retries at command level with
--retries=0. - Do not edit global config just to debug a single test.
Workflow
Phase 1 — Identify What to Test
Determine the feature scope from one of these sources (in priority order):
- Spec file: If a spec is referenced or was just implemented, read it from
.ai/specs/*.mdor.ai/specs/enterprise/*.md. Prefer the new{YYYY-MM-DD}-{slug}.mdfilenames, but tolerate legacy numbered names while the repo is being normalized. Extract testable scenarios from the API Contracts, UI/UX, and Data Models sections. - User description: If the user describes a feature ("test the company creation flow"), map it to the relevant module and pages.
- Recent changes: If triggered after implementation, use
git diffor recent commits to identify changed endpoints, pages, and components.
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.
- 8d ago First seen · 329 lines · 57 tokens per session scan A 0ac45a2207d8
om-integration-tests is a skill published in the GitHub repository SHGrowth/om-superpowers (6 stars, last pushed 5d ago), licensed MIT. It adds 57 tokens to every session and 3,592 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-08-31.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…