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/enterprisegit 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/enterprise)<a href="https://agentmods.dev/rules/omril321/automated-notebooklm/enterprise"><img src="https://agentmods.dev/badge/rules/omril321/automated-notebooklm/enterprise.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.01893 | $0.01893 |
| Opus 5 | $0.00946 | $0.00946 |
| Sonnet 5 | $0.00379 | $0.00379 |
| Haiku 4.5 | $0.00189 | $0.00189 |
Grade A, and why
enterprise 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 4d 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🏢 Enterprise Features for CursorRIPER Σ
Symbol: Ε (Epsilon)
Version: 1.0.0
📋 Enterprise System Definition
service = "Enterprise-grade Features"
symbol = "Ε"
capabilities = "Documentation, Versioning, Compliance, Audit"
📚 Documentation System
Ε_docs = {
generators: {
technical_doc: {
sources: [code_comments, function_signatures, type_definitions],
template: "tech_doc_template.md",
format: ["markdown", "html", "pdf"],
auto_sections: [
"API Reference",
"Architecture Overview",
"Database Schema",
"Integration Points"
]
},
api_doc: {
sources: [api_contracts, request_examples, response_schemas],
template: "api_doc_template.md",
format: ["openapi", "postman", "markdown"],
features: [
"Interactive examples",
"Authentication guide",
"Rate limits",
"Error codes"
]
},
user_guide: {
sources: [user_stories, acceptance_criteria, ui_screenshots],
template: "user_guide_template.md",
format: ["markdown", "html", "pdf", "video"],
sections: [
"Getting Started",
"Features",
"Troubleshooting",
"FAQ"
]
}
},
automation: {
triggers: [
"on_commit",
"on_pr_merge",
"on_release",
"on_gate_completion"
],
rules: {
code_change: regenerate(technical_doc),
api_change: regenerate(api_doc) ∧ notify(consumers),
ui_change: update(user_guide) ∧ capture_screenshots(),
release: generate_all() ∧ version_tag()
}
}
}
🔢 Versioning System
Ε_version = {
strategy: "semantic_versioning",
format: {
pattern: "MAJOR.MINOR.PATCH",
pre_release: "-alpha|-beta|-rc",
build_metadata: "+build.timestamp"
},
rules: {
major: breaking_changes() ∨ api_incompatible(),
minor: new_features() ∧ backwards_compatible(),
patch: bug_fixes() ∧ no_api_changes()
},
branches: {
develop: {
version_suffix: "-dev",
auto_increment: "patch",
merge_to: "staging"
},
staging: {
version_suffix: "-rc",
auto_increment: "minor",
gate_required: Κ₄,
merge_to: "main"
},
main: {
version_suffix: "",
auto_increment: "manual",
gate_required: Κ₅,
protected: true
}
},
automation: {
tag_creation: on_gate_completion(Κ₅),
changelog_generation: from_commit_messages(),
release_notes: from_prd_and_commits()
}
}
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.
- 4d ago First seen · 347 lines · 1,893 tokens per session scan A 22aa943d385a
enterprise 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,893 tokens to every session, about $0.0095 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.