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/mcp-github)<a href="https://agentmods.dev/rules/omril321/automated-notebooklm/mcp-github"><img src="https://agentmods.dev/badge/rules/omril321/automated-notebooklm/mcp-github/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/mcp-github"><img src="https://agentmods.dev/badge/rules/omril321/automated-notebooklm/mcp-github.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.00979 | $0.00979 |
| Opus 5.5 | $0.00392 | $0.00392 |
| Sonnet 5.5 | $0.00196 | $0.00196 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
mcp-github 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 1mo 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🐙 GitHub MCP Integration for CursorRIPER Σ
Symbol: Θ (Theta)
Version: 1.0.0
📋 Service Definition
service = "GitHub Operations"
symbol = "Θ"
requires = "@modelcontextprotocol/server-github"
🔧 Operation Mapping
Θ_ops = {
repo: {
create: "@modelcontextprotocol-server-github:create_repository",
search: "@modelcontextprotocol-server-github:search_repositories",
fork: "@modelcontextprotocol-server-github:fork_repository",
clone: "git clone via get_file_contents"
},
branch: {
create: "@modelcontextprotocol-server-github:create_branch",
list: "@modelcontextprotocol-server-github:list_commits",
checkout: "via create_branch with from_branch"
},
file: {
create: "@modelcontextprotocol-server-github:create_or_update_file",
push: "@modelcontextprotocol-server-github:push_files",
get: "@modelcontextprotocol-server-github:get_file_contents"
},
pr: {
create: "@modelcontextprotocol-server-github:create_pull_request",
review: "@modelcontextprotocol-server-github:create_pull_request_review",
merge: "@modelcontextprotocol-server-github:merge_pull_request",
list: "@modelcontextprotocol-server-github:list_pull_requests"
},
issue: {
create: "@modelcontextprotocol-server-github:create_issue",
update: "@modelcontextprotocol-server-github:update_issue",
comment: "@modelcontextprotocol-server-github:add_issue_comment",
list: "@modelcontextprotocol-server-github:list_issues"
}
}
🔒 Mode Restrictions
MΘ = {
Ω₁: [search_*, list_*, get_*], # RESEARCH: read-only
Ω₂: [search_*, list_*, get_*, fork_repository], # INNOVATE: read + fork
Ω₃: [all_ops], # PLAN: all operations
Ω₄: [create_*, update_*, push_*, merge_*], # EXECUTE: write ops
Ω₅: [get_*, list_*, search_*] # REVIEW: read-only
}
🔑 Permission Matrix
ℙΘ = {
create: [Ω₃, Ω₄],
read: [Ω₁, Ω₂, Ω₃, Ω₄, Ω₅],
update: [Ω₃, Ω₄],
delete: [Ω₃]
}
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.
- 1mo ago First seen · 127 lines · 979 tokens per session scan A 6f3b8f08dac4
mcp-github is a cursor rule published in the GitHub repository omril321/automated-notebooklm (14 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 979 tokens to every session, about $0.0039 per session on Opus 5.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
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.
git-workflow
Git commit format and PR process - conventional commits.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.