AGENTS.md ยท diff

git:20261110.f000740 to git:20261111.0edafa4

1 added, 1 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

# AGENTS.md
This repo packages the Antithesis skills as one plugin, `plugins/antithesis`, for each agent platform.
## Checks
[mise](https://mise.jdx.dev) installs the tools and runs the checks that CI runs. Run `mise run fix` to apply automatic fixes, then `mise run check` before you finish. `mise tasks` lists each `check:<tool>` and `fix:<tool>` task. `check:docs` uses the `snouty` on your PATH. In Claude Code, a Stop hook (`.claude/hooks/fix_and_check.py`) runs both at the end of every turn. mise only runs a `mise.toml` you trust: run `mise trust` once in each checkout, or add the repo to mise's `trusted_config_paths` setting to cover its worktrees too.
### Token budgets
The token budgets that `check:tokens` enforces are soft. When a change goes over one, look for a shorter way to say the same thing: cut statements and words that aren't needed, and rely more on `snouty --help` and `snouty docs` than on restating them. Never trade the design for the budget. Don't change how pages reference each other, move content to another module, or leave out something important just to fit. If the right version is over budget, raise that module's budget in `mise.toml` (`MODULE_TOKEN_BUDGETS`), and say so in the change.
## Cross-references
- A skill page names another file by its path from the skill root, in backticks, such as `references/workload/driver.md`. It names a part of a page by that part's heading, or by the bold label that opens a list item, in double quotes: "Starting up" in `references/workload/driver.md`, the "Wait until every node is up" step in `references/workload/driver.md`, "Write the title and body" in the `open-pr` skill, or just "Report" for a part of the same page. Never refer to a step by its number, such as "step 2": reordering the list would silently change what it points at. Give the step a bold label and name that instead. Put any other quoted text that starts with a capital letter in backticks, so it isn't read as a reference. `check:references` fails on a reference that doesn't resolve, and on any step number.
+ A skill page names another file by its path from the skill root, in backticks, such as `references/workload/driver.md`. It names a part of a page by that part's heading, or by the bold label that opens a list item, in double quotes: "Starting up" in `references/workload/driver.md`, the "Wait until every node is up" step in `references/workload/driver.md`, "Write the title and body" in the `open-pr` skill, or just "Report" for a part of the same page. A table row counts as a part too, named by its first cell: the "Go build image" row in `references/workload/images.md`. A Dockerfile names a base image by its row in that table, as `<Go build image>`. Never refer to a step by its number, such as "step 2": reordering the list would silently change what it points at. Give the step a bold label and name that instead. Put any other quoted text that starts with a capital letter in backticks, so it isn't read as a reference. `check:references` fails on a reference that doesn't resolve, and on any step number.
## Scripts
Write repo tooling in Python, not shell. The scripts under `scripts/` and `.claude/hooks/` run on a uv-managed Python with the dependencies in `pyproject.toml`, locked in `uv.lock`. Each is executable with a `#!/usr/bin/env -S uv run --quiet --locked` shebang, so run it directly, such as `scripts/check.py typos`. Add a dependency with `uv add`, which updates both files. ruff and pyright check the Python.