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/smaramwbc/statewave-connectors/agents-mdgit clone --depth 1 https://github.com/smaramwbc/statewave-connectorsWrote 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-connectors/agents-md)<a href="https://agentmods.dev/instructions/smaramwbc/statewave-connectors/agents-md"><img src="https://agentmods.dev/badge/instructions/smaramwbc/statewave-connectors/agents-md.svg" alt="Measured on agentmods" 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.00721 | $0.00721 |
| Opus 5 | $0.00360 | $0.00360 |
| Sonnet 5 | $0.00144 | $0.00144 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
statewave-connectors 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 5d 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 — 60 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 statewave-connectors — the pnpm monorepo of source
connectors (GitHub, Markdown, Slack, …) and the
Statewave MCP server
(@statewavedev/mcp-server) that feed and serve Statewave memory.
Setup, build, test
See the README for canonical setup. In short:
pnpm install
pnpm -r --filter "./packages/**" run build
pnpm -r --filter "./packages/**" run test
Packages are released with Changesets — add a changeset for any user-facing change.
Conventions
- Code style & testing: see statewave-docs/dev/conventions.md.
- Each connector package versions independently on its own cadence (see the package changesets); don't tie them to the server version.
- Pick subjects deliberately — the single most important connector decision. Follow the subject strategy (stable, low-cardinality identifiers; one primary subject per episode).
- Keep claims accurate and modest in docs and examples.
Pull requests
Keep PRs focused, add a changeset for user-facing changes, and make sure the build and tests pass.
Optional: give your agent memory of this repo (with Statewave)
This repo is the connector + MCP tooling, and the IDE companion is built right
here in packages/vscode-extension. The easiest way to give your assistant a
queryable project brain is that Statewave IDE Companion extension for
VS Code / Cursor (publisher statewavedev) — install it from your editor's
extensions marketplace. It exposes your workspace, docs, git state, structure,
and run-commands to Copilot / Cursor / Claude over MCP and registers the MCP
server for you (no manual config); it just needs a Statewave server to talk to
(a one-file docker compose up). See the
extension README.
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.
- 5d ago First seen · 60 lines · 721 tokens per session scan A b729a6ad9a46
statewave-connectors AGENTS.md is an instructions file published in the GitHub repository smaramwbc/statewave-connectors (3 stars, last pushed 5d ago), licensed Apache-2.0. It adds 721 tokens to every session, about $0.0036 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-31.
Other instructions, from other repositories
statewave-web AGENTS.md
AGENTS.md instructions for smaramwbc/statewave-web: Statewave memory — MCP server statewave, subject repo:smaramwbc.statewave-web. Before answering questions about this project, call statewavegetcontext (that subject, query = the ask) and ground your answer in it. When the user states a durable fact or decision, call…
aeon CLAUDE.md
Claude Code instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
cognirepo CLAUDE.md
Claude Code instructions for ashlesh-t/cognirepo, covering claude.md, key rules, session start sequence (run in this order), behavioral confirmation rule and personas (cognirepo-402, cognirepo-403).
wayland-core copilot-instructions.md
Copilot instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
mcp-structured-memory CLAUDE.md
Claude Code instructions for nmeierpolys/mcp-structured-memory, a project described as: Structured Memory MCP Server.
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.