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/bmad-roles)<a href="https://agentmods.dev/rules/omril321/automated-notebooklm/bmad-roles"><img src="https://agentmods.dev/badge/rules/omril321/automated-notebooklm/bmad-roles.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.1 | $0.01961 | $0.01961 |
| Opus 5 | $0.00981 | $0.00981 |
| Sonnet 5 | $0.00392 | $0.00392 |
| Haiku 4.5 | $0.00196 | $0.00196 |
Grade A, and why
bmad-roles 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 8d 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 โ 264 lines โ stays where its author put it; the contents beside it link to each section on GitHub.
๐ฅ BMAD Role System for CursorRIPER ฮฃ
Symbol: ฮ (Beta)
Version: 1.0.0
๐ Role Definition System
service = "BMAD Role Management"
symbol = "ฮ"
transforms = "Memory-bank โ PRD-driven development"
๐ญ Role Mappings
ฮ_roles = {
ฮโ: {
name: "Product Owner",
primary_modes: [ฮฉโ, ฮฉโ],
responsibilities: [
"Define business objectives",
"Create user stories",
"Set acceptance criteria",
"Approve PRD documents"
],
artifacts: [
"PRD documents",
"User stories",
"Acceptance criteria",
"Success metrics"
],
permissions: โ_read โช โ_create(ฮก)
},
ฮโ: {
name: "Architect",
primary_modes: [ฮฉโ, ฮฉโ],
responsibilities: [
"Design system architecture",
"Define technical standards",
"Create API contracts",
"Review technical designs"
],
artifacts: [
"Technical specifications",
"System design documents",
"API contracts",
"Architecture diagrams"
],
permissions: โ_all - โ_delete(production)
},
ฮโ: {
name: "Developer",
primary_modes: [ฮฉโ, ฮฉโ],
responsibilities: [
"Implement features",
"Write unit tests",
"Create documentation",
"Code reviews"
],
artifacts: [
"Source code",
"Unit tests",
"Technical documentation",
"Code commits"
],
permissions: โ_standard โช โ_execute
},
ฮโ: {
name: "QA Engineer",
primary_modes: [ฮฉโ, ฮฉโ
],
responsibilities: [
"Create test plans",
"Execute test cases",
"Report bugs",
"Verify fixes"
],
artifacts: [
"Test plans",
"Test cases",
"Bug reports",
"QA signoff"
],
permissions: โ_read โช โ_create(tests) โช โ_update(issues)
},
ฮโ
: {
name: "DevOps",
primary_modes: [ฮฉโ, ฮฉโ
],
responsibilities: [
"Manage CI/CD",
"Deploy applications",
"Monitor systems",
"Incident response"
],
artifacts: [
"Deployment configs",
"CI/CD pipelines",
"Monitoring dashboards",
"Runbooks"
],
permissions: โ_all
}
}
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.
- 8d ago First seen ยท 264 lines ยท 1,961 tokens per session scan A cd0021babf0b
bmad-roles 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,961 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.