Borrowing it
Nothing to install: this file belongs to Cipher208/a-memory. 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/Cipher208/a-memory/master/.windsurfrulesgit clone --depth 1 https://github.com/Cipher208/a-memoryWrote 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/rules/cipher208/a-memory/windsurfrules)<a href="https://agentmods.dev/rules/cipher208/a-memory/windsurfrules"><img src="https://agentmods.dev/badge/rules/cipher208/a-memory/windsurfrules.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.00484 | $0.00484 |
| Opus 5 | $0.00242 | $0.00242 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
windsurfrules 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 today.
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-Memory Integration Rules
This project uses ai-memory for codebase context management.
Quick Commands
# Initialize (one-time per project)
ai-memory init
# Full scan (run after major changes)
ai-memory scan
# Watch mode (auto-update on file changes)
ai-memory watch
# Ask about the codebase (low-token context)
ai-memory ask "<your question>"
# Semantic search (run `ai-memory embed` first)
ai-memory semantic "<query>"
# Symbol context with call graph
ai-memory context <symbol_name>
# Reverse call graph � who calls this symbol
ai-memory callers <symbol>
# Full-text search over names/signatures/docstrings
ai-memory search "<query>"
# Detect circular dependencies
ai-memory cycles
# Full inheritance chain for a class
ai-memory inherits <class_name>
# Public API surface
ai-memory api
# See execution flows
ai-memory flows
# See code communities/modules
ai-memory communities
# Find dead/unused code
ai-memory dead-code
# Review changed files and impacted flows
ai-memory review
# Extract TODO/FIXME/HACK markers
ai-memory todos
# Map tests to implementation
ai-memory test-map
# Dependency manifests
ai-memory deps
# Load coverage data
ai-memory coverage
# Build semantic embeddings
ai-memory embed
# Incremental embeddings (only new/changed symbols)
ai-memory embed --incremental
Guidelines for AI Assistants
- Before answering questions, use
ai-memory askorai-memory semanticto get pre-computed context. - When modifying code, check
ai-memory reviewto see which flows and communities are impacted. - For new features, consult
ai-memory communitiesto find the right module to extend. - For debugging, use
ai-memory context <symbol>to trace call chains from entry points. - To find where code is tested, use
ai-memory test-map. - To find public APIs, use
ai-memory api. - To search by keyword, use
ai-memory search "auth middleware".
Project Structure (from ai-memory communities)
Check ai-memory communities for the latest module boundaries.
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.
- today First seen · 89 lines · 484 tokens per session scan A e50a1a39fda4
windsurfrules is a cursor rule published in the GitHub repository Cipher208/a-memory (0 stars, last pushed today), licensed MIT. It adds 484 tokens to every session, about $0.0024 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-09-07.
Other cursor rules, from other repositories
04-spatial-parser
Guidelines for Spatial RAG and Markdown parsing.
memory-reflex
Pensyve memory reflex — the non-optional reasoning discipline for working-memory substrate.
memory-informed-longitudinal-work
Long-running multi-session work (research, eval loops, iterative benchmarks) — resume prior lessons, capture per-run outcomes, build up stable truths over time.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
context-loader
Use when starting a new substantive conversation or switching contexts — load relevant memories to prime the session with continuity.
memory-informed-debug
Use when diagnosing bugs, errors, failing tests, or crashes — consult prior debug outcomes and capture root causes in-flight.