Borrowing it
Nothing to install: this file belongs to smaramwbc/statewave. 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/smaramwbc/statewave/main/AGENTS.mdgit clone --depth 1 https://github.com/smaramwbc/statewaveWrote 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/smaramwbc/statewave/agents-md)<a href="https://agentmods.dev/instructions/smaramwbc/statewave/agents-md"><img src="https://agentmods.dev/badge/instructions/smaramwbc/statewave/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/smaramwbc/statewave/agents-md"><img src="https://agentmods.dev/badge/instructions/smaramwbc/statewave/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.01020 | $0.01020 |
| Opus 5.5 | $0.00408 | $0.00408 |
| Sonnet 5.5 | $0.00204 | $0.00204 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade A, and why
statewave 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 20d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — guide for contributors and coding agents
A short orientation for humans and AI coding agents (GitHub Copilot, Claude, Cursor, …) working in the statewave core repo. For the full contribution process and licensing, start with CONTRIBUTING.md.
What this repo is
Statewave is an open-source memory/context service for AI agents: it records
episodes, compiles them into durable memories, and serves compact, ranked,
token-bounded context over a /v1 API. This repo is the server and reference
implementation. For the big picture, see the
architecture overview.
Setup, build, test
The canonical steps live in CONTRIBUTING.md and the README Quickstart — don't duplicate them, follow them. In short:
docker compose up db -d
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev,llm]"
alembic upgrade head
pytest tests/
Dependencies are locked. CI and the published image install from uv.lock, not
from a fresh resolve of pyproject.toml, and CI runs uv lock --check. So if
you change anything under [project.dependencies] or
[project.optional-dependencies], refresh the lockfile in the same commit:
uv lock
A dependency change without that refresh will not go green.
Run ruff and the test suite before opening a PR; make test-cold validates a
full fresh-install path.
Tip for agents: unit tests are hermetic with stub providers — run them without external services via:
STATEWAVE_EMBEDDING_PROVIDER=stub STATEWAVE_COMPILER_TYPE=heuristic \
pytest tests/ --ignore=tests/integration
Conventions
- Code style & testing: see statewave-docs/dev/conventions.md.
- Packages version independently. The server, the Python SDK (
statewave), and the TypeScript SDK (@statewavedev/sdk) version on separate cadences; the compatibility axis is the/v1API contract, not a shared number. Don't try to align version strings across packages. - Some "proof" numbers are mirrored across repos — test counts, eval
assertion/test counts, and the support-workflow benchmark score. They have a
single source of truth and a consistency check in
statewave-docsthat runs at release time. If you change one of these numbers, keep every surface in sync rather than editing a single file. - Keep claims accurate and modest. Describe what the code does; back any performance or benchmark claim with a reproducible source, and avoid unqualified superlatives.
- CI enforces a few cross-cutting invariants — tenant-scoped repository queries, bounded pagination params, and a single shared tokenizer. If a guard test fails, satisfy the rule rather than weakening the test. See CONTRIBUTING.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.
- 20d ago Changed · +11 lines · +87 tokens per session d0ec43bca93b
- 2mo ago First seen · 81 lines · 933 tokens per session scan A e51d7e751aa2
statewave AGENTS.md is an instructions file published in the GitHub repository smaramwbc/statewave (271 stars, last pushed today), licensed Apache-2.0. It adds 1,020 tokens to every session, about $0.0041 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-08-30.
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).
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.
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).
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 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).
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.