Antithesis plugin
The Antithesis plugin gives a coding agent an entry point to any task involving Antithesis.
Prerequisites
The plugin needs Docker or Podman with Docker Compose, jq, and Snouty CLI.
# Check Docker (or Podman) with Compose, and jqdocker compose versionjq --version
# Install the Snouty CLIcurl --proto '=https' --tlsv1.2 -LsSf https://github.com/antithesishq/snouty/releases/latest/download/snouty-installer.sh | shInstallation
# Claude Codeclaude plugin marketplace add antithesishq/antithesis-pluginclaude plugin install antithesis@antithesis
# Codexcodex plugin marketplace add antithesishq/antithesis-plugincodex plugin add antithesis@antithesisUsing Devin or Replit? See the Devin or Replit setup.
Usage
The Antithesis plugin provides a skill called /antithesis (or $antithesis in some agents). The skill should be invoked automatically for Antithesis related prompts.
In general, you’ll want to prompt the agent with one of the following workflows:
- Write a new workload for system S
- Add functionality to existing workload W
- Define or import a property into workload W
- Launch workload W
- Triage test run R
- Root cause failure F
The skill is designed to be composable, so feel free to ask your agent to chain multiple things together:
/antithesis write a workload for https://github.com/etcd-io/etcd which imports properties from https://antithesis.com/docs/resources/kv_property_catalog.md. You can consume up to 200 compute hours of testing. Use short smoke tests to verify the workload before switching to soak tests to verify etcd. Triage the results, root cause high confidence failures, and file issues for anything new you discover.