Skip to content

Repository files navigation

antithesis-plugin

This plugin gives a coding agent an entry point to any task involving Antithesis.

Generally, you'll want to include a prompt of the form "Use Antithesis to test this PR, then triage and debug any failures you find."

Install

  • Claude Code:
    • claude plugin marketplace add antithesishq/antithesis-plugin
    • claude plugin install antithesis@antithesis
  • Codex:
    • codex plugin marketplace add antithesishq/antithesis-plugin
    • codex plugin add antithesis@antithesis
  • GitHub Copilot CLI:
    • copilot plugin marketplace add antithesishq/antithesis-plugin
    • copilot plugin install antithesis@antithesis
  • Devin: docs/devin.md
  • Replit: docs/replit.md
  • Cursor: docs/cursor.md

Prerequisites

The Antithesis Plugin requires the following tools to be installed.

In addition, Snouty must be authenticated with your Antithesis tenant: snouty login. You can check that Snouty is setup correctly by running snouty doctor.

Recommended model

We test and use the plugin mainly with Claude Opus 5.5 at medium effort, and recommend it. Other models, such as OpenAI Sol, work, but have been seen to issue many safety refusals.

The plugin tests and fuzzes software comprehensively, so its work can trigger a model's safety refusals. Access to OpenAI Daybreak or Anthropic's Cyber Verification Program reduces them.

Usage

The Antithesis plugin provides a skill called /antithesis (or $antithesis in some harnesses). The skill should be invoked automatically for Antithesis related prompts.

Given a free-form prompt, such as /antithesis test the latest release of my system, the skill plans a workflow: the chain of the tasks below that gets from what exists to what you asked for. Common shapes are setting up a new system, healing a workload after its system changed, and testing a system and triaging what breaks.

Or prompt the agent with one of the tasks directly:

  • 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.

Key differences from Antithesis docs

  • Uses Hegel as the generator that drives the system under test, not Antithesis' native test composer.
  • Focuses on reaching coverage of all surfaces in the system under test first, rather than leading with system properties.

Managing compute consumption

Antithesis bills by compute hours, so consider giving your agent a compute hour budget to spend, per run or overall. Keep your system's setup fast too: every run spends that time before fuzzing starts, so a faster setup makes every Antithesis run shorter. See the Antithesis docs on usage for details.

Getting help


Privacy policy • Support email