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 antithesishq/antithesis-skills --skill antithesis-launchgit clone --depth 1 https://github.com/antithesishq/antithesis-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/antithesishq/antithesis-skills/antithesis-launch)<a href="https://agentmods.dev/skills/antithesishq/antithesis-skills/antithesis-launch"><img src="https://agentmods.dev/badge/skills/antithesishq/antithesis-skills/antithesis-launch/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/antithesishq/antithesis-skills/antithesis-launch"><img src="https://agentmods.dev/badge/skills/antithesishq/antithesis-skills/antithesis-launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00081 | $0.01370 |
| Opus 5 | $0.00041 | $0.00685 |
| Sonnet 5 | $0.00016 | $0.00274 |
| Haiku 4.5 | $0.00008 | $0.00137 |
Grade A, and why
antithesis-launch 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 2d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Antithesis Launch
Skill version: 2026-09-08 2e4a837
Prerequisites
- DO NOT PROCEED if
snoutyis not installed. Seehttps://raw.githubusercontent.com/antithesishq/snouty/refs/heads/main/README.mdfor installation options. - Run
snouty doctor. It checks the container runtime and the compose CLI. Report both to the user and build with that same pair. This skill writesdocker compose; usedocker-composeinstead when that is the CLI snouty names.
Goal
Launch an Antithesis run in this order only:
docker compose build(skip if directed to use pre-built images)snouty validate- if validation fails, stop and report the error
snouty launch
Required Input
durationin minutes is required. If the user did not provide it, ask before submitting the run.
Discovery
- Start from any user-provided path, command, or Antithesis directory name.
- Otherwise, inspect the repo to understand how the harness is wired. Check nearby
AGENTS.md,README*,Makefile*, and Antithesis-specific scripts before choosing commands. - Find the config directory by locating the
docker-compose.yamlintended for Antithesis. Prefer directories likeantithesis/config, but support non-standard layouts. - Treat these as strong Antithesis signals: nearby
scratchbook/ortest/directories, compose content mentioning/opt/antithesis,ANTITHESIS_env vars,setup_complete, or existingsnoutyexamples. - If multiple compose files look plausible, prefer the one referenced by repo docs or existing
snouty launchexamples. If the choice is still ambiguous, ask the user instead of guessing. - Use the directory containing
docker-compose.yamlas thesnouty validate <CONFIG>andsnouty launch --config <CONFIG>argument. - Build against that exact file:
docker compose -f <CONFIG>/docker-compose.yaml build. - snouty never builds or pulls images, so every image must already be in the store of the engine snouty selects. snouty prefers podman when both engines are installed.
- Use
SNOUTY_CONTAINER_ENGINE=dockerto force snouty to use docker's store.
- Use
- When using podman, build with
podman compose -f <CONFIG>/docker-compose.yaml build. That wrapper execs Docker Compose v2 against podman's API socket, so the image lands in podman's store. Check the provider first:podman compose versionmust printDocker Compose version ..., because podman falls back to thepodman-composePython tool when it finds no Compose v2 binary.
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.
- 2d ago Changed · +3 lines 0c50cf0b3c5a
- 7d ago Changed 772e31a01ca5
- 11d ago First seen · 92 lines · 81 tokens per session scan A 7a3e2824369f
antithesis-launch is a skill published in the GitHub repository antithesishq/antithesis-skills (267 stars, last pushed 2d ago), licensed Apache-2.0. It adds 81 tokens to every session and 1,370 once invoked, about $0.0004 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.