Borrowing it
Nothing to install: this file belongs to quailyquaily/aqua. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/quailyquaily/aqua/master/AGENTS.mdgit clone --depth 1 https://github.com/quailyquaily/aquaWrote 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.
[](https://agentmods.dev/instructions/quailyquaily/aqua/agents-md)<a href="https://agentmods.dev/instructions/quailyquaily/aqua/agents-md"><img src="https://agentmods.dev/badge/instructions/quailyquaily/aqua/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.
<a href="https://agentmods.dev/instructions/quailyquaily/aqua/agents-md"><img src="https://agentmods.dev/badge/instructions/quailyquaily/aqua/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00567 | $0.00567 |
| Opus 5 | $0.00283 | $0.00283 |
| Sonnet 5 | $0.00113 | $0.00113 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
aqua 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
cmd/aqua/main.go: CLI entrypoint (aqua) and command wiring.aqua/: core Aqua domain logic (identity, contacts, RPC, node/session behavior).internal/fsstore/: file-backed storage primitives (atomic writes, JSON/JSONL helpers, locks, indexing).docs/: operator-facing docs (architecture.md,cli.md).- Tests live next to implementation files and use
*_test.go.
Build, Test, and Development Commands
go build -o ./bin/aqua ./cmd/aqua: build the CLI binary.go run ./cmd/aqua --help: run locally without a manual build.go test ./...: run all unit tests (baseline check before every PR).go test -race ./...: run race detector for concurrency/storage-sensitive changes.go test ./aqua -run TestExtractRPCIDForError: run a focused test during iteration.
Tip: isolate local state during manual testing:
AQUA_DIR=$(mktemp -d) go run ./cmd/aqua init
Coding Style & Naming Conventions
- Language target is Go (
go.moduses Go 1.24.x); always format withgofmt. - Follow Go naming: exported identifiers in
PascalCase, internal helpers incamelCase. - Keep package names short/lowercase (
aqua,fsstore) and files organized by concern (*_test.gomirrors production files). - Prefer wrapped errors with context (
fmt.Errorf("...: %w", err)), especially at storage/network boundaries.
Testing Guidelines
- Use the standard
testingpackage with clearTest...names describing behavior. - Prefer table-driven tests plus
t.Run(...)for variants. - Use
t.Parallel()where safe andt.TempDir()for filesystem isolation. - Cover both success and failure paths (invalid input, decode errors, lock/path failures).
Commit & Pull Request Guidelines
- Use Conventional Commits (for example:
feat(aqua): add protocol history lookup,fix(fsstore): reject invalid lock key). - Keep commits scoped and include related tests/docs in the same change.
- PRs should include: purpose, impacted paths, test commands run, and linked issue (if any).
- For CLI behavior changes, include sample command/output snippets in the PR description.
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.
- 11d ago First seen · 42 lines · 567 tokens per session scan A 512d873987b4
aqua AGENTS.md is an instructions file published in the GitHub repository quailyquaily/aqua (259 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 567 tokens to every session, about $0.0028 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.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.