antithesis · git:20261107.35c08e5 · 2026-11-07 · sha256 fe3ee3fd3af8fdca

antithesis git:20261107.35c08e5A

Immutable. This exact content never changes and is served at /api/v1/blob/fe3ee3fd3af8fdca.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_26jh6mkrkx3ovigh/fe3ee3fd3af8fdcaf6ba2d6f9b6be6bb7b0d2ce9804b75688cd78ab57c4ebbd2.json

Then /plugin install antithesis@markdownregistry-26jh6mkrkx3ovigh in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: antithesis
description: Entry point to Antithesis. Use for any task that involves Antithesis.
argument-hint: "[triage [monitor|summary|root-cause]|debug|workload|launch|properties] [target]"
---

# Antithesis

Plugin version: `0.0.9`

## Before starting

1. If you are running on one of these platforms, read its notes:
   - Devin: `references/platforms/devin.md`
   - Replit: `references/platforms/replit.md`
2. Read `references/antithesis/explainer.md`.
3. Check the dependencies below.

### Dependencies

Every module needs:

- **snouty 0.9.0 or later**, installed and configured for the Antithesis tenant. If it's missing or not configured, follow `references/antithesis/snouty-setup.md`. If it's older, run `snouty update`, or reinstall it if it wasn't installed with the installer script
- **Docker or Podman, with Docker Compose**
- **jq**

Assume that dependencies are setup. If any command fails, check dependencies and `snouty doctor` first.

## Modules

Pick the module from the first argument, then read only that module's `MODULE.md`.

| Argument     | Module                            | Use when                                                      |
| ------------ | --------------------------------- | ------------------------------------------------------------- |
| `triage`     | `references/triage/MODULE.md`     | Analyze a run for failures, monitor an in progress run.       |
| `debug`      | `references/debug/MODULE.md`      | Execute commands in Antithesis to debug a moment or property. |
| `workload`   | `references/workload/MODULE.md`   | Building or iterating on a workload.                          |
| `launch`     | `references/launch/MODULE.md`     | Launching a new run of a workload with `snouty launch`.       |
| `properties` | `references/properties/MODULE.md` | Importing the SUT's guarantees or defining a new one.         |

If there is no argument, infer the module from the request. If it is still ambiguous, ask.

Once you've read the module's `MODULE.md`, if the task will run unattended for a long time, such as building a workload or launching and following runs, ask the user up front, in one message, for anything you can foresee needing: a compute budget, permission to change their code, the scope, where to report issues, and any choice the module leaves to the user. Then keep working toward the user's goal, within the budget, until it is met or you are blocked on something only the user can decide. A module's steps are a means to the goal, not its end. While other work remains, don't end your turn on a question: write it in a file the user will see, tell them where, and keep working.