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/omril321/automated-notebooklm/prd-systemgit 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/prd-system)<a href="https://agentmods.dev/rules/omril321/automated-notebooklm/prd-system"><img src="https://agentmods.dev/badge/rules/omril321/automated-notebooklm/prd-system.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 | $0.01706 | $0.01706 |
| Opus 5 | $0.00853 | $0.00853 |
| Sonnet 5 | $0.00341 | $0.00341 |
| Haiku 4.5 | $0.00171 | $0.00171 |
Grade A, and why
prd-system 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 3d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📄 PRD System for CursorRIPER Σ
Symbol: Ρ (Rho)
Version: 1.0.0
📋 PRD Definition System
service = "Product Requirements Document System"
symbol = "Ρ"
driver = "Transform memory-bank → PRD-driven methodology"
📐 PRD Components
Ρ = {
Ρ₁: {
name: "Business Objectives",
required: true,
template: "objectives_template.md",
owner: Β₁,
validation: [measurable, time_bound, aligned]
},
Ρ₂: {
name: "Functional Requirements",
required: true,
template: "requirements_template.md",
owner: Β₁,
validation: [specific, testable, prioritized]
},
Ρ₃: {
name: "Technical Constraints",
required: true,
template: "constraints_template.md",
owner: Β₂,
validation: [feasible, documented, approved]
},
Ρ₄: {
name: "User Stories",
required: true,
template: "story_template.md",
owner: Β₁,
validation: [sized, estimated, acceptance_defined]
},
Ρ₅: {
name: "Acceptance Criteria",
required: true,
template: "acceptance_template.md",
owner: Β₁ ∪ Β₄,
validation: [measurable, complete, testable]
},
Ρ₆: {
name: "Success Metrics",
required: true,
template: "metrics_template.md",
owner: Β₁,
validation: [quantifiable, trackable, relevant]
}
}
📁 PRD Structure
/prd/
├── active/
│ ├── current_prd.md # Ρ_active
│ ├── metadata.json # Version, status, approvals
│ └── components/
│ ├── objectives.md # Ρ₁
│ ├── requirements.md # Ρ₂
│ ├── constraints.md # Ρ₃
│ ├── stories/ # Ρ₄
│ ├── acceptance/ # Ρ₅
│ └── metrics.md # Ρ₆
├── templates/
│ ├── prd_master.md
│ ├── objectives_template.md
│ ├── requirements_template.md
│ ├── constraints_template.md
│ ├── story_template.md
│ ├── acceptance_template.md
│ └── metrics_template.md
└── archive/
└── [version]/ # Historical PRDs
🔄 Memory Bank Migration
σ_to_Ρ_migration = {
σ₁: { // projectbrief.md
migrate_to: Ρ₁,
transform: extract_objectives(),
preserve: backup_original()
},
σ₂: { // systemPatterns.md
migrate_to: Β₂_artifacts,
transform: convert_to_arch_docs(),
link: reference_in_Ρ₃
},
σ₃: { // techContext.md
migrate_to: Ρ₃,
transform: structure_constraints(),
enhance: add_validation_rules()
},
σ₄: { // activeContext.md
migrate_to: Γ_prd ∪ Γ_roles,
transform: separate_contexts(),
maintain: real_time_sync()
},
σ₅: { // progress.md
migrate_to: Κ_gates ∪ Ρ₆,
transform: convert_to_metrics(),
track: gate_completion_status()
},
σ₆: { // protection.md
maintain: no_change,
integrate: apply_to_PRD_sections()
}
}
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.
- 3d ago First seen · 275 lines · 1,706 tokens per session scan A c210c51db44c
prd-system is a cursor rule published in the GitHub repository omril321/automated-notebooklm (15 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 1,706 tokens to every session, about $0.0085 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.