Borrowing it
Nothing to install: this file belongs to smaramwbc/statewave-connectors. 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-connectors/main/packages/vscode-extension/.github/copilot-instructions.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/copilot-instructions)<a href="https://agentmods.dev/instructions/smaramwbc/statewave-connectors/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/smaramwbc/statewave-connectors/copilot-instructions/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-connectors/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/smaramwbc/statewave-connectors/copilot-instructions.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.00340 | $0.00340 |
| Opus 5.5 | $0.00136 | $0.00136 |
| Sonnet 5.5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
statewave-connectors copilot-instructions.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 1mo 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.
What it actually says
Statewave project memory
This workspace has a Statewave “project brain” exposed over MCP (server id: statewave). It holds this project's summary, conventions, documentation, git history, code structure and remembered facts, scoped to subject workspace:statewave.
Read it first
Before answering questions about THIS project — conventions, architecture, history, structure, prior decisions, “how/why does X work”, “what changed” — call the statewave_get_context MCP tool (subject workspace:statewave, query = the user's ask) and ground your answer in what it returns. Prefer it over guessing or re-deriving from scratch.
Persist durable facts
When the user states a durable preference, decision, or fact worth remembering across sessions (e.g. “my favorite color is red”, “we use X for Y”, “always do Z here”), call the statewave_ingest_episode MCP tool (subject workspace:statewave, kind chat.note, text = the fact). Capture stable facts/preferences/decisions only — not transient chatter, and not code you are about to write. The user sees and can approve each tool call.
Immediately after a successful statewave_ingest_episode, call the statewave_compile_subject MCP tool (subject workspace:statewave). An ingested episode is raw and not yet retrievable; compiling distils it into the durable memory that statewave_get_context returns next time.
Never invent Statewave results; if the tool is unavailable, say so plainly.
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.
- 1mo ago First seen · 18 lines · 340 tokens per session scan A 6451717b89dd
statewave-connectors copilot-instructions.md is an instructions file published in the GitHub repository smaramwbc/statewave-connectors (4 stars, last pushed 5d ago), licensed Apache-2.0. It adds 340 tokens to every session, about $0.0014 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-31.
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.