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 agentmods add skills/archimedes-run/omniharness/smoke-testnpx skills add archimedes-run/omniHarness --skill smoke-testgit clone --depth 1 https://github.com/archimedes-run/omniHarnessWhat 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 | $0.00100 | $0.02108 |
| Opus 5 | $0.00050 | $0.01054 |
| Sonnet 5 | $0.00020 | $0.00422 |
| Haiku 4.5 | $0.00010 | $0.00211 |
Grade A, and why
smoke-test 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 yesterday.
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.
This is a copy
86% identical to smoke-test — 29 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OmniHarness Smoke Test Skill
This skill guides the Agent through OmniHarness's full end-to-end smoke test workflow, including code updates, deployment (supporting both Docker and local installation modes), service availability verification, and health checks.
Deployment Mode Selection
This skill supports two deployment modes:
- Local installation mode (recommended, especially when network issues occur) - Run all services directly on the local machine
- Docker mode - Run all services inside Docker containers
Selection strategy:
- If the user explicitly asks for Docker mode, use Docker
- If network issues occur (such as slow image pulls), automatically switch to local mode
- Default to local mode whenever possible
Structure
smoke-test/
├── SKILL.md ← You are here - core workflow and logic
├── scripts/
│ ├── check_docker.sh ← Check the Docker environment
│ ├── check_local_env.sh ← Check local environment dependencies
│ ├── frontend_check.sh ← Frontend page smoke check
│ ├── pull_code.sh ← Pull the latest code
│ ├── deploy_docker.sh ← Docker deployment
│ ├── deploy_local.sh ← Local deployment
│ └── health_check.sh ← Service health check
├── references/
│ ├── SOP.md ← Standard operating procedure
│ └── troubleshooting.md ← Troubleshooting guide
└── templates/
├── report.local.template.md ← Local mode smoke test report template
└── report.docker.template.md ← Docker mode smoke test report template
Standard Operating Procedure (SOP)
Phase 1: Code Update Check
- Confirm current directory - Verify that the current working directory is the OmniHarness project root
- Check Git status - See whether there are uncommitted changes
- Pull the latest code - Use
git pull origin mainto get the latest updates - Confirm code update - Verify that the latest code was pulled successfully
What ships with it
11 files 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.
- references/SOP.md 9.7 KB
- references/troubleshooting.md 11 KB
- scripts/check_docker.sh 2.0 KB runs code
- scripts/check_local_env.sh 2.4 KB runs code
- scripts/deploy_docker.sh 1.7 KB runs code
- scripts/deploy_local.sh 1.5 KB runs code
- scripts/frontend_check.sh 2.0 KB runs code
- scripts/health_check.sh 3.1 KB runs code
- scripts/pull_code.sh 1.2 KB runs code
- templates/report.docker.template.md 4.5 KB
- templates/report.local.template.md 4.6 KB
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.
- yesterday First seen · 182 lines · 0 tokens per session scan A b5f7bbd32432
smoke-test is a skill published in the GitHub repository archimedes-run/omniHarness (6 stars, last pushed 6d ago), licensed MIT. It adds 100 tokens to every session and 2,108 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to smoke-test, differing in 29 lines, and is treated as a copy.
Other skills, from other repositories
debugging-output-and-previewing-html-using-ray
Use when user says "send to Ray," "show in Ray," "debug in Ray," "log to Ray," "display in Ray," or wants to visualize data, debug output, or show diagrams in the Ray desktop application.
changelog-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".
project-snmp-profiles-authoring
Use when editing Netdata SNMP profile YAMLs, topology SNMP profiles, ddsnmp profile parsing, or profile-format documentation. Requires checking source MIB field accessibility, especially MAX-ACCESS not-accessible INDEX objects, before adding or changing profile symbols.
fix-issues
Fix a batch of open GitHub issues end to end - one git worktree and one agent per issue (feature-dev for implementation, review-pr for review), individual PRs into develop, a release PR to main with a final multi-agent integration review, and optional tag/release/issue-comment publishing. Use when the user asks to…
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
kurtosis-ethereum
Run Ethereum multi-client devnets using Kurtosis and the ethpandaops/ethereum-package. Use for spinning up local devnets, syncing public testnets, validating cross-client interop, testing fork transitions, shadowforks, running assertoor checks, debugging CL/EL client interactions, or verifying new feature…