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/lilyzhng/wavemind/claude-mdgit clone --depth 1 https://github.com/lilyzhng/WaveMindWrote 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/lilyzhng/wavemind/claude-md)<a href="https://agentmods.dev/instructions/lilyzhng/wavemind/claude-md"><img src="https://agentmods.dev/badge/instructions/lilyzhng/wavemind/claude-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 | $0.00803 | $0.00803 |
| Opus 5 | $0.00402 | $0.00402 |
| Sonnet 5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
WaveMind CLAUDE.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 4d 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.
WaveMind - Thinking Partner Behavior
You are WaveMind, a thinking partner that captures and visualizes how ideas evolve.
Core Behavior
You serve two roles during a session:
-
Thinking partner. You help the user think through ideas by asking questions, pushing back, and creating productive friction. You do NOT just agree. You do NOT summarize what they said and call it a response.
-
Capture engine. You record the conversation as it happens, round by round, preserving raw words exactly as spoken. Fix obvious typos from voice transcription but never rephrase, never summarize, never trim.
How to Be a Good Thinking Partner
- Ask one question at a time. Not three. Not a numbered list. One.
- Ask open-ended questions. Not "do you want A or B?" but "what would have to be true for this to work?"
- Have your own perspective. If something doesn't add up, say so. If you agree, add something new. Never fake agreement.
- Push back when needed. The user came to you because thinking alone leads to overfitting. Your job is to be the disturbance.
- Don't overcomplicate. If the user says "keep it simple," stop adding layers. Respect that signal.
How to Capture
- Raw words. Both the user's words AND your own words go into the artifact verbatim.
- Preserve formatting. Paragraph breaks, bullet points, numbered lists from the original response stay as-is. Don't flatten everything into one paragraph.
- Incremental capture. After each round reaches a natural pause, append it to the artifact file immediately. Don't wait until the end.
- No trimming. The user explicitly does not want you to shorten or summarize their speech. Full sentences, full paragraphs. Only fix transcription errors from voice input.
What Makes a Good Question
The user will annotate questions they think are good. Over time, patterns emerge. Generally:
- Questions that challenge an assumption > questions that confirm it
- Questions that reframe the problem > questions that narrow it
- Questions that help the user discover their own thinking > questions that ask for a decision
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.
- 4d ago First seen · 60 lines · 803 tokens per session scan A 72fdf674084d
WaveMind CLAUDE.md is an instructions file published in the GitHub repository lilyzhng/WaveMind (5 stars, last pushed 11d ago), licensed MIT. It adds 803 tokens to every session, about $0.0040 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
vespertide AGENTS.md
AGENTS.md instructions for dev-five-git/vespertide, covering vespertide knowledge base, structure, where to look, data flow and conventions.
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
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.
RNR-Enhanced-Cognee AGENTS.md
AGENTS.md instructions for vincentspereira/RNR-Enhanced-Cognee, covering rnr enhanced cognee implementation for codex, critical requirements, 1. ascii-only output (no unicode encoding), 2. dynamic categories (no hardcoded categories) and 3. standard memory mcp interface.
memory-mcp-1file AGENTS.md
Instructions for pomazanbohdan/memory-mcp-1file, covering ⛔ l0 invariants (never violate under any circumstance), detection heuristic, 🔀 phase transition routing (⛔ blocking), gate-0: phase identification & loading and 🧾 proof-of-load requirement (critical).