Borrowing it
Nothing to install: this file belongs to archimedes-run/omniHarness. 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/archimedes-run/omniHarness/main/.agent/skills/smoke-test/SKILL.mdgit clone --depth 1 https://github.com/archimedes-run/omniHarnessWrote 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/archimedes-run/omniharness/smoke-test)<a href="https://agentmods.dev/skills/archimedes-run/omniharness/smoke-test"><img src="https://agentmods.dev/badge/skills/archimedes-run/omniharness/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/archimedes-run/omniharness/smoke-test"><img src="https://agentmods.dev/badge/skills/archimedes-run/omniharness/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.00000 | $0.02108 |
| Opus 5.5 | $0.00000 | $0.00843 |
| Sonnet 5.5 | $0.00000 | $0.00422 |
| Haiku 4.5 | $0.00000 | $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 1mo 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.
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.
- 1mo ago First seen · 182 lines · 0 tokens per session scan A b5f7bbd32432
smoke-test is a skill published in the GitHub repository archimedes-run/omniHarness (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,108 tokens. 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
testing-patterns
Testing patterns for Spring Boot - JUnit 5, Mockito, MockMvc, Testcontainers, positive and negative test cases. Use when user asks about testing, writing tests, test coverage, or test failures.
test-runner
For a code change, pick the right test tier by change surface, run apc test with baseline diff, and report only NEW reds vs baseline back to the task's acceptance criterion. Separates envblocked from SUT red so a broken machine never fails the code.
webapp-qa
Perform scoped exploratory QA of a web application, reproduce defects, collect screenshots and console evidence, and deliver a prioritized report.
lipas-e2e
Run end-to-end scenarios against a live LIPAS dev system. Use when verifying a user-visible flow works correctly across DB, Elasticsearch, app-db, and DOM. Covers municipality-user flows (create/update sports facility) and grows from there.
bmad-agent-qa
QA engineer for test automation and coverage. Use when the user asks to talk to Quinn or requests the QA engineer.
branchbox-devcontainer-guardrails
Use when modifying BranchBox devcontainer/bootstrap workflows, compose templates, feature env-stash behavior, or manual E2E harness/release docs. Apply issue.