wave: Instructions file for Codex

AGENTS.md

wave AGENTS.md is an instructions file for Codex, OpenCode from re-cinq/wave. It costs 4,725 tokens per session, scanned B, original, MIT.

A project instruction file for Wave, a Go program that coordinates multiple AI coding agents and command-line tools. It explains the project's architecture, development rules, testing expectations, and security constraints.

In plain words
What is it for?
Use it when developing Wave's agents, pipelines, command-line integrations, contracts, security checks, or tests.
Why use it?
It gives an agent the context needed to change a multi-agent system without breaking its contracts or runtime behavior. It also requires problems found during work to be fixed and validated.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions AGENTS.md.

This is re-cinq/wave's own configuration. It tells Codex and OpenCode how to work on wave itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything wave configures →

Reuse

Borrowing it

Nothing to install: this file belongs to re-cinq/wave. 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/re-cinq/wave/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/re-cinq/wave

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.

agentmods badge for wave AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/re-cinq/wave/agents-md/github.svg)](https://agentmods.dev/instructions/re-cinq/wave/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/re-cinq/wave/agents-md"><img src="https://agentmods.dev/badge/instructions/re-cinq/wave/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.

agentmods 80×15 button for wave AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/re-cinq/wave/agents-md"><img src="https://agentmods.dev/badge/instructions/re-cinq/wave/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,725 This file is loaded in full into every session.
When invoked 4,725 The same file — it is already loaded in full.
Security scan B 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.04725 $0.04725
Opus 5.5 $0.01890 $0.01890
Sonnet 5.5 $0.00945 $0.00945
Haiku 4.5 $0.00473 $0.00473

Measured 1mo ago against content hash 796e02e2d5f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

wave AGENTS.md scanned grade B with 1 finding 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 1mo 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

6. Check for leaked files: `gh pr diff <N> --name-only | grep -E "^\.claude/|^\.agents/artifacts/|^\.agents/output/"`
AGENTS.md · 303 lines

How it starts

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

Wave Development Guidelines

Wave is a multi-agent pipeline orchestrator written in Go that wraps Claude Code and other LLM CLIs via subprocess execution. It composes personas, pipelines, contracts, and relay/compaction into a continuous development system.

ACCOUNTABILITY — YOU FOUND IT, YOU FIX IT

URGENT — NON-NEGOTIABLE: This is the single most important rule in this file. It survives context compaction. Re-read it if you are unsure.

If you discover a problem — any problem — you own it. Fix it immediately.

There is NO concept of "pre-existing issue" in this project. If you touched it or saw it break — fix it.

If a validation step reveals issues in files you didn't modify — fix those too.

Never argue about whether something is your responsibility.

Critical Constraints

  1. Single static binary — no runtime dependencies except adapter binaries
  2. Test ownership — every failing test is YOUR concern. Fix or delete (with justification), never ignore. Changes to personas, pipelines, contracts, or meta-pipelines require go test ./...
  3. Security first — all inputs validated, paths sanitized, permissions enforced
  4. Constitutional compliance — navigator-first architecture, fresh memory at step boundaries, contract validation at handovers, ephemeral workspace isolation, observable progress events
  5. Observable execution — structured progress events for monitoring
  6. No backward compatibility constraint during prototype phase — move fast, let tests catch regressions
  7. No t.Skip() without a linked issue. Delete tests only with clear justification

How Wave Works at Runtime

Each pipeline is a topologically-sorted DAG of steps. For every step:

  1. Workspace creation — an ephemeral worktree is created under .agents/workspaces/<pipeline>/<step>/. Steps can share workspaces via workspace.ref. Mounts support readonly/readwrite modes
  2. Artifact injection — outputs from prior steps are injected into .agents/artifacts/ before execution begins. The system validates existence, enforces optional/required semantics, and checks schemas if ref.SchemaPath is specified
  3. Runtime CLAUDE.md assembly — a per-step CLAUDE.md is generated from four layers:
    • Base protocol preamble (.agents/personas/base-protocol.md)
    • Persona system prompt (role, responsibilities, constraints)
    • Contract compliance section (auto-generated from step contract schema)
    • Restriction section (denied/allowed tools, network domains from manifest permissions)
  4. Adapter execution — the persona runs in isolated context with fresh memory (no chat history inheritance)
  5. Contract validation — step output is validated against its contract (json_schema, typescript_interface, test_suite, markdown_spec, format) before marking the step successful. Hard failures block; soft failures log warnings

Read the full file on GitHub · 303 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.

  1. 1mo ago First seen · 303 lines · 4,725 tokens per session scan B 796e02e2d5f9

Subscribe to this mod's changes

wave AGENTS.md is an instructions file published in the GitHub repository re-cinq/wave (23 stars, last pushed 1mo ago), licensed MIT. It adds 4,725 tokens to every session, about $0.0189 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens