a2wave AGENTS.md

Repository instructions for a2wave, an enterprise platform for building and running AI agents through APIs, chat tools, schedules, and code repositories. They describe its structure, technology, commands, and required checks.

In plain words
What is it for?
Working on a2wave’s API, web app, command-line tool, or shared code in its pnpm monorepo—a repository containing several related projects managed together.
Why use it?
They give coding agents the project’s rules and boundaries, reducing mistakes such as using the wrong command, language, or security approach.

Instructions file for CodexOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/lilithgames/a2wave/agents-md
Clone the repo
git clone --depth 1 https://github.com/LilithGames/a2wave

Made for: Codex, OpenCode.

Per session 1,499 This file is loaded in full into every session.
When invoked 1,499 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.01499 $0.01499
Opus 5 $0.00749 $0.00749
Sonnet 5 $0.00300 $0.00300
Haiku 4.5 $0.00150 $0.00150

Measured 2d ago against content hash 90c791fa92f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

a2wave 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 2d 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 · 81 lines

How it starts

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

a2wave — Project Guide

Natural-language-driven Agent orchestration: a general-purpose Agent building and orchestration platform for enterprises, published over API / Feishu / Slack / Discord / A2A / scheduled / chat page / GitLab & GitHub repository triggers.

Primary language: English. This is an OSS-facing repository — all code, comments, commit messages, documentation, and identifiers must be written in English.

Trust model: Agent authors and users are trusted colleagues; controls enforce accountability and least privilege, not containment of a hostile insider — never harden against a malicious authenticated author, and never skip auth, anonymous-invoke, drop an audit entry, or put credentials in details. Full statement: trust model & Iron Rules · SECURITY.md.

Architecture

a2wave (pnpm monorepo)
├── apps/api/         # Hono + SQLite (Drizzle ORM) + Local Agent Execution
├── apps/web/         # React 19 + Vite + TailwindCSS v4 + Ant Design
├── apps/cli/         # CLI tool (a2wave command)
└── packages/shared/  # Zod schemas & types

Stack: TypeScript, Biome (lint), TanStack Query, React Router v7, Vitest + Playwright.

Product boundary

Six Iron Rules define what a2wave will and will not build — check every new feature against them first: docs/agent/iron-rules.md. Violations need maintainer sign-off before proceeding.

Commands

pnpm install          # install
cp .env.example .env  # leave AUTH_SECRET empty — pnpm dev generates one
pnpm run dev          # API :3502 + Web :3501 (override with PORT / WEB_PORT)
pnpm stop             # free the ports if a previous run left orphans
pnpm test             # all unit/integration tests
pnpm db:migrate       # run migrations for the DATABASE_URL backend

Setup detail, database backends, worktree conventions: docs/agent/development.md.

Gates — non-negotiable, --no-verify forbidden

Read the full file on GitHub · 81 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. 2d ago First seen · 81 lines · 1,499 tokens per session scan A 90c791fa92f2

Subscribe to this mod's changes

a2wave AGENTS.md is an instructions file published in the GitHub repository LilithGames/a2wave (24 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,499 tokens to every session, about $0.0075 per session on Opus 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-08-30.