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/xingjiantao/cursor-rules-for-pytorch-deeplearning-beginner/memory-bank-taskmastergit clone --depth 1 https://github.com/XingjianTao/Cursor-Rules-for-PyTorch-DeepLearning-BeginnerWrote 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/xingjiantao/cursor-rules-for-pytorch-deeplearning-beginner/memory-bank-taskmaster)<a href="https://agentmods.dev/rules/xingjiantao/cursor-rules-for-pytorch-deeplearning-beginner/memory-bank-taskmaster"><img src="https://agentmods.dev/badge/rules/xingjiantao/cursor-rules-for-pytorch-deeplearning-beginner/memory-bank-taskmaster.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.01815 | $0.01815 |
| Opus 5 | $0.00907 | $0.00907 |
| Sonnet 5 | $0.00363 | $0.00363 |
| Haiku 4.5 | $0.00181 | $0.00181 |
Grade A, and why
memory-bank-taskmaster 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.
This is a copy
95% identical to common_memory_bank — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: globs: alwaysApply: true
Cursor's Memory Bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read ALL memory bank files at the start of EVERY task - this is not optional.
Memory Bank Structure
The Memory Bank consists of required core files and optional context files, all in Markdown format. 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
PB & PC & SP & TC --> PRD[prd.txt]
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
-
systemPatterns.md- System architecture
- Key technical decisions
- Design patterns in use
- Component relationships
-
techContext.md- Technologies used
- Development setup
- Technical constraints
- Dependencies
Additional Context
Create additional files/folders within memory-bank/ when they help organize:
- Complex feature documentation
- Integration specifications
- API documentation
- Testing strategies
- Deployment procedures
Taskmaster Tool Synchronization
When Taskmaster Tool (MCP or task-master CLI commands) is used, Taskmaster Tool and Memory Bank must be synchronized. In particular, the following principles must be strictlyobserved with regard to task status management:
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 · 213 lines · 1,815 tokens per session scan A 6b09cc94c06b
memory-bank-taskmaster is a cursor rule published in the GitHub repository XingjianTao/Cursor-Rules-for-PyTorch-DeepLearning-Beginner (3 stars, last pushed 1y ago), licensed MIT. It adds 1,815 tokens to every session, about $0.0091 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to common_memory_bank, differing in 8 lines, and is treated as a copy.
Other cursor rules, from other repositories
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
common_memory_bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…
context-recorder-system
Context Recorder System (记录员系统) - 模块化索引文件.
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.