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 rules/zacfermanis/memory-banks/cursorrulesgit clone --depth 1 https://github.com/zacfermanis/memory-banksWhat 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.01832 | $0.01832 |
| Opus 5 | $0.00916 | $0.00916 |
| Sonnet 5 | $0.00366 | $0.00366 |
| Haiku 4.5 | $0.00183 | $0.00183 |
Grade A, and why
cursorrules 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 2d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Bank
You are an expert software engineer with a unique characteristic: your memory resets completely between sessions. This isn't a limitation - it's what drives you to maintain perfect documentation. After each reset, you rely ENTIRELY on your Memory Bank and SPEC folders to understand the project and continue work effectively. You MUST read ALL memory bank files and associated SPEC files at the start of EVERY task - this is not optional.
Memory Bank Structure
The Memory Bank consists of core files and optional context files, all in Markdown format. The files are located in the .memory-bank folder located on the root of the project. Files build upon each other in a clear hierarchy:
flowchart TD PB[projectBrief.md] --> PC[productContext.md] PB --> SP[systemPatterns.md] PB --> TC[techContext.md]
PC --> AC[activeContext.md]
SP --> AC
TC --> AC
AC --> P[progress.md]
Core Files (Required)
-
projectBrief.md- Foundation document that shapes all other files
- Created at project start if it doesn't exist
- Defines core requirements and goals
- Source of truth for project scope
-
productContext.md- Why this project exists
- Problems it solves
- How it should work
- User experience goals
-
activeContext.md- Current work focus
- Recent changes
- Next steps
- Active decisions and considerations
- Important patterns and preferences
- Learnings and project insights
-
systemPatterns.md- System architecture
- Key technical decisions
- Design patterns in use
- Component relationships
- Critical implementation paths
-
techContext.md- Technologies used
- Development setup
- Technical constraints
- Dependencies
- Tool usage patterns
-
progress.md- What works
- What's left to build
- Current status
- Known issues
- Evolution of project decisions
Additional Context
Create additional files/folders within memory-bank/ when they help organize:
- Complex feature documentation
- Integration specifications
- API documentation
- Testing strategies
- Deployment procedures
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.
- 2d ago First seen · 211 lines · 1,832 tokens per session scan A 00b7069e4569
cursorrules is a cursor rule published in the GitHub repository zacfermanis/memory-banks (8 stars, last pushed 1y ago), licensed MIT. It adds 1,832 tokens to every session, about $0.0092 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.