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/omril321/automated-notebooklmWrote 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/omril321/automated-notebooklm/cursor-riper-date-conciseness-standards)<a href="https://agentmods.dev/rules/omril321/automated-notebooklm/cursor-riper-date-conciseness-standards"><img src="https://agentmods.dev/badge/rules/omril321/automated-notebooklm/cursor-riper-date-conciseness-standards/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/omril321/automated-notebooklm/cursor-riper-date-conciseness-standards"><img src="https://agentmods.dev/badge/rules/omril321/automated-notebooklm/cursor-riper-date-conciseness-standards.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.00579 | $0.00579 |
| Opus 5 | $0.00290 | $0.00290 |
| Sonnet 5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
cursor-riper-date-conciseness-standards 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Bank Standards: Date Accuracy & Content Conciseness
🎯 Purpose
This roll ensures memory bank files maintain accurate dates and concise content when working with the CursorRIPER♦Σ memory system.
📅 Date Accuracy Standards
Required Actions
-
Always check current date before updating any memory bank file:
date -
Use exact current date in "Updated" field:
_v1.X | Created: YYYY-MM-DD | Updated: 2025-07-08_ -
Never assume or remember dates from previous sessions
Validation
- ✅ Date format: DD-MM-YYYY
- ✅ Date is current (not from previous sessions)
- ✅ All memory bank files use same date for batch updates
📝 Content Conciseness Standards
Memory Bank Content Rules
- High-level overview only - No implementation details
- Patterns and decisions - Not code examples
- Essential information - Not verbose explanations
- Reference to code - Not duplicate code content
Content Validation Checklist
Before updating memory bank files, verify:
- ❓ Is this information essential for project context?
- ❓ Does this belong in code/docs instead?
- ❓ Can this be expressed more concisely?
- ❓ Is this a decision/pattern or implementation detail?
Specific Guidelines by File Type
Tech Context (σ₃)
- ✅ Architecture patterns and decisions
- ✅ Technology stack overview
- ✅ Key design patterns (without implementation)
- ❌ Detailed code examples
- ❌ Configuration file contents
- ❌ Verbose API documentation
Progress Tracker (σ₅)
- ✅ Status and milestones
- ✅ Completed tasks summary
- ✅ Next steps overview
- ❌ Detailed implementation steps
- ❌ Code snippets
- ❌ Verbose technical explanations
Active Context (σ₄)
- ✅ Current focus and decisions
- ✅ Immediate tasks and priorities
- ✅ Context references
🚨 Common Mistakes to Avoid
Content Issues for techContext.md and progress.md
- ❌ Copying code blocks into memory bank
- ❌ Including verbose implementation details
- ❌ Duplicating content from code files
- ❌ Adding configuration examples
- ❌ Including detailed API documentation
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.
- 10d ago First seen · 102 lines · 579 tokens per session scan A a6f00310c139
cursor-riper-date-conciseness-standards is a cursor rule published in the GitHub repository omril321/automated-notebooklm (15 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 579 tokens to every session, about $0.0029 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
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
A modular system for recording project context, decisions, requirements, and lessons in structured files. It divides the recorder into core, template, advanced, and edge-case modules.
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.