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 dorayo/orchestrix-skills --skill smoke-testgit clone --depth 1 https://github.com/dorayo/orchestrix-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/dorayo/orchestrix-skills/smoke-test)<a href="https://agentmods.dev/skills/dorayo/orchestrix-skills/smoke-test"><img src="https://agentmods.dev/badge/skills/dorayo/orchestrix-skills/smoke-test/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/dorayo/orchestrix-skills/smoke-test"><img src="https://agentmods.dev/badge/skills/dorayo/orchestrix-skills/smoke-test.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.00046 | $0.01012 |
| Opus 5 | $0.00023 | $0.00506 |
| Sonnet 5 | $0.00009 | $0.00202 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
smoke-test scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **HTTP** (`curl`) — assert status code AND response content (a 200 How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smoke Test (Prove It Works From the Outside)
Unit tests prove functions; a smoke test proves the PRODUCT. Launch the real app and walk the real flows the user will walk.
Core principle: A flow is "passed" only when you drove it yourself and captured the evidence. "The tests are green so it probably works" is a claim, not a smoke test.
The Iron Law
UNTESTED IS NOT PASSED. Every flow ends in exactly one of:
passed (with evidence) | failed (with evidence) | untested (with the reason)
Process
- Discover how to run it.
registry/appfirst; else the project's manifest (package.jsonscripts,Makefile,README). If the launch method is genuinely undocumented and unguessable, reportuntested: cannot launch— do not invent a server. - Launch in the background, capture logs. Redirect stdout/stderr to
.orchestrate/verify/smoke-server.log. Record the PID. Pick a free port if configurable (avoid colliding with anything already running). - Wait for readiness, bounded. Poll the health endpoint / port / ready
line for up to ~60s. Not ready → flow verdicts are
failed: app did not start, attach the server log, skip to cleanup. - Exercise EVERY listed flow with the best driver available, in order of
fidelity:
- Browser automation (a Playwright/Chrome MCP tool, if available in this session) — for UI flows: navigate, interact, assert on rendered state, screenshot.
- HTTP (
curl) — assert status code AND response content (a 200 serving an error page is a fail; check for a string the flow implies). - CLI — invoke the command, assert exit code and output.
Use the highest-fidelity driver the flow needs: an interactive UI flow
"verified" by curling
/isuntested, notpassed.
- Capture evidence per flow to
.orchestrate/verify/smoke-<flow-slug>.log(the exact command/steps + relevant output tail, or the screenshot path). - ALWAYS clean up — kill the processes you started (and only those), remove temp state you created. Cleanup runs even when flows fail.
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 Changed · +1 lines 75b7eb8bbc6b
- 11d ago First seen · 91 lines · 46 tokens per session scan A 931a45a0eb30
smoke-test is a skill published in the GitHub repository dorayo/orchestrix-skills (2 stars, last pushed 8d ago), licensed MIT. It adds 46 tokens to every session and 1,012 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…