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/quality-gatesgit 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/quality-gates)<a href="https://agentmods.dev/rules/omril321/automated-notebooklm/quality-gates"><img src="https://agentmods.dev/badge/rules/omril321/automated-notebooklm/quality-gates.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.01962 | $0.01962 |
| Opus 5 | $0.00981 | $0.00981 |
| Sonnet 5 | $0.00392 | $0.00392 |
| Haiku 4.5 | $0.00196 | $0.00196 |
Grade A, and why
quality-gates 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.
How it starts
The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚦 Quality Gates for CursorRIPER Σ
Symbol: Κ (Kappa)
Version: 1.0.0
📋 Gate System Definition
service = "Enterprise Quality Gate System"
symbol = "Κ"
enforcement = "Sequential gate progression with approvals"
🎯 Gate Definitions
Κ = {
Κ₁: {
name: "PRD Approval Gate",
phase: "Requirements",
blockers: {
prd_completeness: 100%,
objectives_clear: validated(Ρ₁),
requirements_complete: validated(Ρ₂),
stories_estimated: all(Ρ₄.estimation > 0),
acceptance_defined: all(Ρ₅.criteria.length > 0)
},
approvers: [Β₁],
artifacts_required: [
"Complete PRD document",
"User story backlog",
"Success metrics defined"
],
next: Κ₂,
rollback: draft_state
},
Κ₂: {
name: "Design Review Gate",
phase: "Architecture",
blockers: {
architecture_documented: exists(tech_spec),
api_contracts_defined: validated(api_spec),
security_review_passed: security_score > 80,
performance_targets_set: defined(sla_metrics),
database_design_complete: exists(data_model)
},
approvers: [Β₂],
artifacts_required: [
"Technical specification",
"Architecture diagrams",
"API documentation",
"Security assessment"
],
next: Κ₃,
rollback: Κ₁
},
Κ₃: {
name: "Code Review Gate",
phase: "Implementation",
blockers: {
tests_passing: test_suite.pass_rate === 100%,
coverage_threshold: code_coverage > 80%,
linting_passed: lint_errors === 0,
no_security_vulnerabilities: security_scan.critical === 0,
documentation_complete: api_docs_generated()
},
approvers: [Β₃, Β₄],
artifacts_required: [
"Source code",
"Unit tests",
"Integration tests",
"Code documentation"
],
next: Κ₄,
rollback: development_branch
},
Κ₄: {
name: "QA Signoff Gate",
phase: "Testing",
blockers: {
acceptance_tests_passed: acceptance_suite.pass_rate === 100%,
regression_suite_clean: regression_failures === 0,
performance_benchmarks_met: all(perf_metrics < threshold),
accessibility_compliant: a11y_score > 90,
browser_compatibility: all(browsers.tested)
},
approvers: [Β₄],
artifacts_required: [
"Test execution reports",
"Bug tracking status",
"Performance reports",
"QA signoff document"
],
next: Κ₅,
rollback: Κ₃
},
Κ₅: {
name: "Deployment Approval Gate",
phase: "Release",
blockers: {
staging_validation_complete: staging_tests.passed,
rollback_plan_documented: exists(rollback_procedure),
monitoring_configured: all(alerts.configured),
runbooks_updated: documentation.current,
change_approval_obtained: change_ticket.approved
},
approvers: [Β₅],
artifacts_required: [
"Deployment plan",
"Rollback procedures",
"Monitoring configuration",
"Release notes"
],
next: production_release,
rollback: Κ₄
}
}
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 · 297 lines · 1,962 tokens per session scan A be32d4811380
quality-gates is a cursor rule published in the GitHub repository omril321/automated-notebooklm (15 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 1,962 tokens to every session, about $0.0098 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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.