Borrowing it
Nothing to install: this file belongs to HazAT/pi-interactive-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/HazAT/pi-interactive-subagents/main/.pi/skills/run-integration-tests/SKILL.mdgit clone --depth 1 https://github.com/HazAT/pi-interactive-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/hazat/pi-interactive-subagents/run-integration-tests)<a href="https://agentmods.dev/skills/hazat/pi-interactive-subagents/run-integration-tests"><img src="https://agentmods.dev/badge/skills/hazat/pi-interactive-subagents/run-integration-tests.svg" alt="Measured on agentmods" 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.00055 | $0.02202 |
| Opus 5 | $0.00028 | $0.01101 |
| Sonnet 5 | $0.00011 | $0.00440 |
| Haiku 4.5 | $0.00006 | $0.00220 |
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 7d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Integration Tests
Execute the integration test suite inside cmux, then introspect every spawned session to verify the full subagent lifecycle worked end-to-end.
Step 1: Preflight Checks
Verify the environment is ready:
echo "CMUX_SOCKET_PATH=$CMUX_SOCKET_PATH"
echo "TMUX=$TMUX"
node --version
- At least one of
CMUX_SOCKET_PATHorTMUXmust be set - Node 22+ required
If neither mux is available, stop and tell the user to run inside cmux or tmux.
Step 2: Run Unit Tests
Run the fast unit tests first — if these fail, skip integration tests:
cd /Users/haza/Projects/pi-interactive-subagents && node --test test/test.ts
All 114 unit tests must pass. If any fail, stop and fix them before proceeding.
Step 3: Run Integration Tests
Use cmux to run the integration tests in a dedicated surface so the main session stays responsive.
SURFACE=$(cmux new-surface --type terminal | awk '{print $2}')
sleep 0.5
cmux send --surface $SURFACE 'cd /Users/haza/Projects/pi-interactive-subagents && node --test --test-concurrency=1 test/integration/mux-surface.test.ts test/integration/subagent-lifecycle.test.ts 2>&1; echo __TESTS_DONE_$?__\n'
--test-concurrency=1 is required: the focus-preservation test asserts global mux state and would race against parallel suites.
Poll until the sentinel appears:
cmux read-screen --surface $SURFACE --lines 200
Look for __TESTS_DONE_0__ (success) or __TESTS_DONE_1__ (failure). Poll every 15 seconds. Timeout after 10 minutes.
Once done, capture the full output and close the surface:
cmux read-screen --surface $SURFACE --scrollback --lines 500
cmux close-surface --surface $SURFACE
Expected results
| Suite | Tests | Approx Duration |
|---|---|---|
mux-surface |
8 | ~45s |
subagent-lifecycle |
7 | ~170s |
All 15 tests must pass. If any fail, report the failure output and stop.
The long-running keeps a long active tool call from surfacing false stalled status test in subagent-lifecycle runs ~100s on its own — total wall time is ~3:30.
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.
- 7d ago First seen · 246 lines · 55 tokens per session scan A 04f70fbab6c8
run-integration-tests is a skill published in the GitHub repository HazAT/pi-interactive-subagents (674 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 2,202 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-30.
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.
trailblaze
Use when working with Trailblaze — natural-language device control for coding agents across iOS, Android, and web, with replayable .trail.yaml files as the artifact. Trigger on mentions of Trailblaze, the trailblaze CLI, .trail.yaml files, trailmaps, waypoints, or requests to drive / author / debug / run UI tests on…
Detox Mobile Testing
Gray-box end-to-end testing for React Native apps with Detox. Covers .detoxrc.js configuration, build and test commands, matchers, device.launchApp control, automatic synchronization, and macOS CI pipelines.