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/leshchenko1979/fast-mcp-telegramWrote 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/leshchenko1979/fast-mcp-telegram/memory-bank)<a href="https://agentmods.dev/rules/leshchenko1979/fast-mcp-telegram/memory-bank"><img src="https://agentmods.dev/badge/rules/leshchenko1979/fast-mcp-telegram/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.1 | $0.01623 | $0.01623 |
| Opus 5 | $0.00812 | $0.00812 |
| Sonnet 5 | $0.00325 | $0.00325 |
| Haiku 4.5 | $0.00162 | $0.00162 |
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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- memory-bank — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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. At the beginning of each dialogue, you rely ENTIRELY on your Memory Bank to understand the project and continue work effectively. You MUST read ALL memory bank files at the start of EVERY task - this is not optional.
Memory Bank Structure
The Memory Bank lives in .cursor/memory-bank/ at the project root. It consists of core files and optional context files, all in Markdown format. Files build upon each other in a clear hierarchy with distinct areas of responsibility:
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]
subgraph ".cursor/memory-bank/"
PB
PC
AC
SP
TC
P
end
Core Files (Required) - Clear Areas of Responsibility
The core files live in .cursor/memory-bank/:
-
.cursor/memory-bank/projectbrief.md- Foundation & Scope- 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
- AOR: What the project is and what it should accomplish
-
.cursor/memory-bank/productContext.md- Why & How- Why this project exists
- Problems it solves
- How it should work
- User experience goals
- AOR: Product vision, user needs, and experience design
-
.cursor/memory-bank/activeContext.md- Current Focus & Decisions- Current work focus (1-2 main items)
- Active decisions and considerations
- Important patterns and preferences
- Next immediate steps (3-5 items max)
- AOR: What we're working on right now and why
-
.cursor/memory-bank/systemPatterns.md- Architecture & Design- System architecture
- Key technical decisions
- Design patterns in use
- Component relationships
- Critical implementation paths
- AOR: How the system is structured and why
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.
- 7d ago First seen · 182 lines · 1,623 tokens per session scan A 2851b8905441
memory-bank is a cursor rule published in the GitHub repository leshchenko1979/fast-mcp-telegram (49 stars, last pushed 14d ago), licensed MIT. It adds 1,623 tokens to every session, about $0.0081 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
00-workflow
Before responding to any request, call getsessioncontext.
resume
Resume from last checkpoint with state drift detection — validate persisted assumptions before continuing.
checkpoint
Save a session checkpoint — what was done, what's next, blockers.
note
Quick note — save a thought, decision, or observation to session memory.
100-memory-system
Comprehensive Memory System architecture for autonomous Cursor operation.
nauro-context
Writes durable shared context into Nauro's project store so other agents (a later session or a parallel one) can discover and pull it, finds and reads context another agent left, or captures a resumable brief so your own next session in this environment picks up cleanly. Three modes. Author writes a shared brief for…