memory-bank-manual-qa

memory-bank-manual-qa is a cursor rule for Cursor from omril321/automated-notebooklm. It costs 19 tokens per session (182 once invoked), scanned A, original, Apache-2.0.

A checklist for reviewing memory-bank files, which store the project's current progress and decisions, during the RIPER Sigma process.

In plain words
What is it for?
It guides progress checks, status explanations, identification of missing details, and requests for permission before changing project notes.
Why use it?
It helps recover context when earlier work or the current phase is unclear.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit It guides progress checks, status explanations, identification of missing details, and requests for permission before changing project notes.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/omril321/automated-notebooklm/memory-bank-manual-qa
Install

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.

Clone the repo
git clone --depth 1 https://github.com/omril321/automated-notebooklm

Made for: Cursor.

Wrote 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.

agentmods badge for memory-bank-manual-qa

README.md
[![agentmods](https://agentmods.dev/badge/rules/omril321/automated-notebooklm/memory-bank-manual-qa/github.svg)](https://agentmods.dev/rules/omril321/automated-notebooklm/memory-bank-manual-qa)
Your own site
<a href="https://agentmods.dev/rules/omril321/automated-notebooklm/memory-bank-manual-qa"><img src="https://agentmods.dev/badge/rules/omril321/automated-notebooklm/memory-bank-manual-qa/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.

agentmods 80×15 button for memory-bank-manual-qa

Your own site · 80×15
<a href="https://agentmods.dev/rules/omril321/automated-notebooklm/memory-bank-manual-qa"><img src="https://agentmods.dev/badge/rules/omril321/automated-notebooklm/memory-bank-manual-qa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 182 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00182
Opus 5 $0.00010 $0.00091
Sonnet 5 $0.00004 $0.00036
Haiku 4.5 $0.00002 $0.00018

Measured 10d ago against content hash 1474cf6cad98, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

memory-bank-manual-qa 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 10d 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.

.cursor/rules/manual_rules/memory-bank-manual-qa.mdc · 15 lines

What it actually says

Check the RIPER Sigma framework carefully. Details are at @riper/ripersigma105.mdc .

Also consider the following rules:

  • @cursor-riper-date-conciseness-standards.mdc

Check the memory bank files for the current phase and see where we stand. Check the current progress by reading previous messages and the current changes of the files. If we lost track of the progress, or anything is missing, ask the user for missing details. Once you have the full picture, reflect the situation to the user. Mention where we stand (what's the current mission in high level) and which mode we're at. If there are changes needed to be done to the memory bank files, ask the user for permission to do so.

Changes

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.

  1. 10d ago First seen · 15 lines · 19 tokens per session scan A 1474cf6cad98

Subscribe to this mod's changes

memory-bank-manual-qa is a cursor rule published in the GitHub repository omril321/automated-notebooklm (15 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 182 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-30.