What is sail AGENTS.md?

A repository instruction document for Sail, an orchestration layer that runs coding agents in isolated containers and coordinates work through a shared SQLite control system. It explains the project structure and build, test, integration, and native-binary commands.

Use it when building Sail, running Maven tests and formatting checks, exercising integration tests, or producing its GraalVM native binary.

It gives coding agents the project context and the exact verification steps expected before changes are accepted.

How standardapplied/sail configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to standardapplied/sail. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/standardapplied/sail/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/standardapplied/sail

Made for: Codex, OpenCode.

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

README.md

[![agentmods](https://agentmods.dev/badge/instructions/standardapplied/sail/agents-md/github.svg)](https://agentmods.dev/instructions/standardapplied/sail/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/standardapplied/sail/agents-md"><img src="https://agentmods.dev/badge/instructions/standardapplied/sail/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/standardapplied/sail/agents-md"><img src="https://agentmods.dev/badge/instructions/standardapplied/sail/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,829 This file is loaded in full into every session.

When invoked 1,829 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01829	$0.01829
Opus 5.5	$0.00732	$0.00732
Sonnet 5.5	$0.00366	$0.00366
Haiku 4.5	$0.00183	$0.00183

Measured 5d ago against content hash 17836eda1bbb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sail AGENTS.md 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 5d 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.

AGENTS.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Sail is the orchestration layer around coding agents: one Incus container per project, a SQLite control plane synced between an org's main box and each engineer's node, specs as the unit of work, and a review loop that runs a build, reviewers and fix agents. Java 25, three Maven modules (sail-core, sail-harness, sail-infra), one GraalVM native binary. Design and contracts: ARCHITECTURE.md. Build, gates, migrations, releases: CONTRIBUTING.md.

Build and test

mvn clean verify is the gate CI runs: every unit test, JaCoCo coverage gates, spotless. mvn spotless:apply formats. Build offline with -o when the repository is warm.
Before pushing: mvn -o -Pintegration -Dsail.it.requireIncus=false clean verify. It adds the multi-node integration tests (*IT); the incus-backed ones skip here and run in CI.
One module and class: mvn -o -pl sail-infra -am -Dtest=StageSkillsTest test (-am is required, or sail-core resolves stale from ~/.m2).
Native binary: JAVA_HOME=<graalvm-jdk-25> mvn clean package -Pnative -DskipTests → sail-infra/target/sail.
Log a long verify to a file and read its BUILD line and Tests run: totals; never judge it from a | grep | head pipeline.

Working a spec

Specs live in the sail database. Use the spec CLI (spec board, spec show <id>, spec comment <id> --body <text>, --question when blocked). Never change a spec's status; sail does.
Branch agent/<spec-id>, one pull request, squash-merged. Post progress and the final summary in the spec's room.
No AI attribution anywhere: no Co-Authored-By trailers, no "Generated with" lines.
The pull request body names what the change deleted, with the git diff --shortstat count. A change that only adds is read twice.

Shape of a change

The bar is the same for the agent that builds, the agent that reviews, the agent that fixes findings and the person who merges: a change is judged on what it leaves behind, not only on whether it works. Each of these is a finding at review and a reason not to merge:

Read the full file on GitHub · 116 lines

Changes

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.

5d ago Changed · -1 lines · -7 tokens per session 17836eda1bbb
16d ago Changed · +33 lines · +499 tokens per session f4a0fd000493
29d ago Changed · +2 lines · +43 tokens per session 14761c9a4dde
1mo ago First seen · 82 lines · 1,294 tokens per session scan A 0db55e35aae7

Subscribe to this mod's changes

sail AGENTS.md is an instructions file published in the GitHub repository standardapplied/sail (12 stars, last pushed 4d ago), licensed MIT. It adds 1,829 tokens to every session, about $0.0073 per session on Opus 5.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-10-08.

Testing Writing and docs agent-orchestration ai-agents coding-agent harness

sail AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
sail AGENTS.mdstandardapplied/sail	Instructions file	12	4d ago	MIT	A	1,829	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	275k	3d ago	MIT	A	4,313	Codex, OpenCode

sail: Instructions file for Codex