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/essentialsgit clone --depth 1 https://github.com/pmikutel/directed-memory-bankWhat 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.00211 | $0.00211 |
| Opus 5 | $0.00105 | $0.00105 |
| Sonnet 5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
essentials 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.
What it actually says
Essentials
- No git commits without explicit permission. File edits are fine; running
git commitneeds the user to say so. - Operation-specific routing lives in the per-area rules under
.cursor/rules/— let the rule for the area you're touching fire and load the memory-bank files it names. memory-bank/_index.mdis the inventory of what exists in DMB — consult it when navigating or when authoring a new rule, not as a runtime step on every operation.
Writing into memory-bank/
Follow memory-bank/project/doc-guide.md for style, length, and hygiene before editing any memory-bank file.
Authoring note (delete after customising): this file is intentionally short. Add project-specific essentials only if they truly apply on every Cursor invocation — anything operation-scoped belongs in a path-scoped rule under
.cursor/rules/, not here.
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 · 20 lines · 211 tokens per session scan A 2e1940b7b97f
essentials is a cursor rule published in the GitHub repository pmikutel/directed-memory-bank (5 stars, last pushed 1mo ago), licensed MIT. It adds 211 tokens to every session, about $0.0011 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
contorium-workspace-continuity
Prefer Contorium workspace memory and AI-ready export over re-explaining the whole repository in chat.
01-qa-agent
QA AGENT PERSONA: Principles, Anti-patterns, workflows.
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
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.