Borrowing it
Nothing to install: this file belongs to davidsunglee/pi-mux-subagents. 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/davidsunglee/pi-mux-subagents/main/.pi/skills/run-integration-tests/SKILL.mdgit clone --depth 1 https://github.com/davidsunglee/pi-mux-subagentsWrote 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/davidsunglee/pi-mux-subagents/run-integration-tests)<a href="https://agentmods.dev/skills/davidsunglee/pi-mux-subagents/run-integration-tests"><img src="https://agentmods.dev/badge/skills/davidsunglee/pi-mux-subagents/run-integration-tests/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/davidsunglee/pi-mux-subagents/run-integration-tests"><img src="https://agentmods.dev/badge/skills/davidsunglee/pi-mux-subagents/run-integration-tests.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.00061 | $0.03334 |
| Opus 5.5 | $0.00024 | $0.01334 |
| Sonnet 5.5 | $0.00012 | $0.00667 |
| Haiku 4.5 | $0.00006 | $0.00333 |
Grade A, and why
run-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 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.
How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Integration Tests
Run the current repository's integration suite from the active working tree and capture a test-runner artifact. The workflow is backend-neutral: it supports Herdr, cmux, tmux, zellij, and wezterm. When running inside Herdr, force PI_SUBAGENT_MUX=herdr so pane-backed tests exercise the Herdr adapter.
Inputs and defaults
Determine these before dispatch:
| Input | Default | Notes |
|---|---|---|
| Working directory | current git repo root | Never hardcode a user/path-specific checkout. |
| Suite mode | fast |
fast runs npm run test:integration; all runs PI_RUN_SLOW=1 npm run test:integration; slow-only runs npm run test:integration:slow. |
| Child model | existing PI_TEST_MODEL, else harness default |
If the user names a model, resolve it first; set PI_TEST_MODEL=<fully-qualified-model> for child pi sessions. For pi model thinking, use the pi model suffix form if needed, e.g. openai-codex/gpt-5.4:medium. |
| Test-runner model | crossProvider.cheap via shared dispatch |
If the user explicitly requests a runner model (for example, "GPT-5.4 with medium thinking"), resolve it and pass model, cli, and thinking explicitly to the test-runner subagent. |
| Backend forcing | none | If the user wants Herdr coverage and HERDR_ENV=1, prefix the command with PI_SUBAGENT_MUX=herdr. |
| Timeout | existing PI_TEST_TIMEOUT, else harness default |
Override with PI_TEST_TIMEOUT=<ms> when requested or when running slow/full suites. |
| Session validation | optional, enabled for lifecycle/pane investigations | Validate recent pi-integ-* sessions after the run when requested or when debugging lifecycle behavior. |
Model resolution
When the user names a model without a provider, do not guess. Run:
pi --list-models "<model name>"
- One match: use the fully-qualified provider/model value.
- Multiple matches: prefer an authenticated provider if clear; otherwise ask.
- No match: say so and ask for another model/login.
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 · 292 lines · 61 tokens per session scan A 5688fcb787a3
run-integration-tests is a skill published in the GitHub repository davidsunglee/pi-mux-subagents (2 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 3,334 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
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
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.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
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.