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/pmikutel/directed-memory-bank/memory-bankgit clone --depth 1 https://github.com/pmikutel/directed-memory-bankWrote 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/pmikutel/directed-memory-bank/memory-bank)<a href="https://agentmods.dev/rules/pmikutel/directed-memory-bank/memory-bank"><img src="https://agentmods.dev/badge/rules/pmikutel/directed-memory-bank/memory-bank.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.00021 | $0.01430 |
| Opus 5 | $0.00010 | $0.00715 |
| Sonnet 5 | $0.00004 | $0.00286 |
| Haiku 4.5 | $0.00002 | $0.00143 |
Grade A, and why
memory-bank 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DMB — Cursor entry
DMB is the project's shared knowledge base. This is an Agent-Requested rule — Cursor loads it on demand when the description matches the operation at hand. Description-only frontmatter (no alwaysApply, no globs:) keeps it cheap; the always-on essentials.mdc carries anything that must always be in scope.
Workflow — where to start
Step 1: glance at current work
The memory-bank/tasks/ layer is an optional scratchpad — it may or may not contain relevant context for what you're about to do.
memory-bank/tasks/work/— one file per in-flight topic (idea, plan, active work). May be empty. If nothing relevant exists, that's fine.memory-bank/tasks/log/— one file per completed unit of work (typically one per merged PR). Useful for history / debugging context.memory-bank/tasks/process.md— the workflow for maintainingwork/andlog/.
Do not fabricate entries. If there's nothing in work/ that matches, move on.
Step 2: let path-scoped rules fire
Operation-specific routing lives in the per-area rules under .cursor/rules/ (backend, frontend, migrations, etc.). Each one names the memory-bank files relevant for that area and fires automatically when the editor is touching matching files. Trust them; do not duplicate their work here.
Step 3: navigate when you need to
If you need a file that no path-scoped rule covers — or you're not sure what knowledge the project has captured — read memory-bank/_index.md. It is the inventory of what exists and which files matter for which kind of work. Use it to discover what to load, not as a step taken every session.
The tasks/ layer
What it is
RAM memory for code work. It does not replace Notion, Jira, or any tool that defines what work exists.
work/ — optional scratchpad
One file per topic, human-readable kebab-case slug (e.g., choppy-audio-issue.md). Frontmatter carries state (status, branch, pr, started, updated). A topic's file grows from "idea" through "planned" / "active" and moves to log/ on PR merge.
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 · 109 lines · 21 tokens per session scan A 9006a5539293
memory-bank is a cursor rule published in the GitHub repository pmikutel/directed-memory-bank (5 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 1,430 once invoked, about $0.0001 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.
cli-error-handling
CLI command error handling patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.