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.
git clone --depth 1 https://github.com/mehmetdemirci/comb-aiWrote 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/mehmetdemirci/comb-ai/memory-bank)<a href="https://agentmods.dev/rules/mehmetdemirci/comb-ai/memory-bank"><img src="https://agentmods.dev/badge/rules/mehmetdemirci/comb-ai/memory-bank/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/mehmetdemirci/comb-ai/memory-bank"><img src="https://agentmods.dev/badge/rules/mehmetdemirci/comb-ai/memory-bank.svg" alt="Reviewed on agentmods" width="80" 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.00193 | $0.00193 |
| Opus 5 | $0.00097 | $0.00097 |
| Sonnet 5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00019 | $0.00019 |
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 9d 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
Memory Bank — Cursor Auto-Loader
This
.mdcfile is a Cursor-specific wrapper. Its only job is to auto-inject the shared protocol and rules files into every Cursor session.The actual content lives in plain markdown files that any AI tool can read.
Read These Files
memory-bank-protocol.md— Memory bank methodology, reading strategy, workflows, update protocolproject-rules.md— Project-specific rules, coding standards, constraints + dynamic sprint zonememory-bank/INDEX.md— Routing hub, follow its reading strategy for the current task type
Companion Rules
.cursor/rules/update-memory-bank.mdc— Auto-updates memory bank after task completion.cursor/rules/create-memory-bank.mdc— Initializes memory bank for new projects
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.
- 9d ago First seen · 21 lines · 193 tokens per session scan A ca4336a8f640
memory-bank is a cursor rule published in the GitHub repository mehmetdemirci/comb-ai (13 stars, last pushed 6mo ago), licensed MIT. It adds 193 tokens to every session, about $0.0010 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-30.
Other cursor rules, from other repositories
cursor-memory
Shokunin memory system: persistent context across sessions.
aictx
Cursor rule "aictx" from oldskultxo/aictx, covering aictx, priority model, default loop, inspection and advanced tools and what to record.
react-composition-patterns
React composition patterns for scalable component architecture including compound components, context providers, state management, boolean prop alternatives, render props vs children, and React 19 API changes. Use when refactoring components with many boolean props, building component libraries, designing flexible…
react-rerender-optimization
React re-render optimization patterns including memo, useMemo, useCallback, useState, useRef, and derived state. Use when components re-render too often, dealing with stale closures, dependency arrays, performance issues, or optimizing slow components.
160-workflow-orchestration
WHEN executing tasks MANAGE workflow processes for consistent memory operations.
050-reference-verification-system
description: WHEN referencing memory files ENSURE references are verified for accuracy and relevance globs: ["/.md", "/.mdc"] alwaysApply: true.