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.
npx agentmods add instructions/lightninglabs/wavelength/agents-mdgit clone --depth 1 https://github.com/lightninglabs/wavelengthWhat 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 | $0.01948 | $0.01948 |
| Opus 5 | $0.00974 | $0.00974 |
| Sonnet 5 | $0.00390 | $0.00390 |
| Haiku 4.5 | $0.00195 | $0.00195 |
Grade A, and why
wavelength 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- wavelength CLAUDE.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wavelength Agent Guide
This file is a map, not a manual. Follow links for details.
Quick Commands
| Command | Purpose |
|---|---|
make build |
Compile the project |
make lint-local |
Run full linter locally, no Docker |
make lint-changed-local |
Run local linter on changes vs base |
make lint |
Run linter via Docker (CI canonical) |
make install-custom-gcl |
Build native custom-gcl for this host |
make fmt |
Format all Go source files |
make fmt-changed |
Format changed Go source files |
make fmt-changed-check |
Verify changed Go source files are formatted |
make unit pkg=<pkg> case=<test> |
Run unit tests |
make unit log="stdlog trace" pkg=<pkg> case=<test> |
Unit tests with debug logs |
make systest |
System integration tests (use db=postgres for PostgreSQL) |
make tidy-module-check |
Verify module files are tidy |
make rpc |
Regenerate protobuf stubs |
make sqlc |
Regenerate type-safe DB queries |
make ast-lint |
Check ast-grep style rules |
make commitmsg-lint range="origin/main..HEAD" |
Lint commit messages on the current branch |
make systest |
Run system integration tests (sqlite) |
make systest db=postgres |
Run system integration tests (postgres) |
Code Style (Summary)
- 8-space tabs, 80-char line limit (best effort).
- Every function/method gets a comment starting with its name.
- Exported identifiers need GoDoc comments wrapped to 80 columns.
- Organize code into logical stanzas with explanatory comments between them.
- Function calls: closing
)on its own line when wrapping. - Function definitions: first param on same line, closing
)with last param. - Structured logging: use
InfoS/DebugS/etc. with static messages andslog.Int()/btclog.Fmt()key-value pairs. Seedocs/structured-logging.md. - Production
Warn,Error, andCriticallogs alert a human. Use them only when the event is actionable at that severity. Expected client input, policy rejection, safe fallback, and repeated retry noise belong atInfo/Debug(docs/structured-logging.md).
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.
- 2d ago First seen · 145 lines · 1,948 tokens per session scan A 8394a43a43b3
wavelength AGENTS.md is an instructions file published in the GitHub repository lightninglabs/wavelength (44 stars, last pushed 3d ago), licensed MIT. It adds 1,948 tokens to every session, about $0.0097 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
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 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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.