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/mcp-filesystemgit 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-filesystem)<a href="https://agentmods.dev/rules/omril321/automated-notebooklm/mcp-filesystem"><img src="https://agentmods.dev/badge/rules/omril321/automated-notebooklm/mcp-filesystem.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.01699 | $0.01699 |
| Opus 5 | $0.00849 | $0.00849 |
| Sonnet 5 | $0.00340 | $0.00340 |
| Haiku 4.5 | $0.00170 | $0.00170 |
Grade A, and why
mcp-filesystem 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CursorRIPER♦Σ Filesystem MCP Integration
📁 MCP Filesystem Operations
Φ_fs = { read(path) = mcp_call("read_file", {path}), read_multi(paths) = mcp_call("read_multiple_files", {paths}), write(path, content) = mcp_call("write_file", {path, content}), edit(path, edits, dry_run = false) = mcp_call("edit_file", {path, edits, dryRun: dry_run}), create_dir(path) = mcp_call("create_directory", {path}), list(path) = mcp_call("list_directory", {path}), tree(path) = mcp_call("directory_tree", {path}), move(source, dest) = mcp_call("move_file", {source, destination: dest}), search(path, pattern, exclude = []) = mcp_call("search_files", {path, pattern, excludePatterns: exclude}), info(path) = mcp_call("get_file_info", {path}), allowed() = mcp_call("list_allowed_directories", {}) }
🔌 Mode-Specific Filesystem Operations
MΦ = { Ω₁: Φ_fs[read, read_multi, list, tree, search, info, allowed], // Research Ω₂: Φ_fs[read, list, tree, search, info, allowed], // Innovate Ω₃: Φ_fs[read, list, search, info, create_dir, allowed], // Plan Ω₄: Φ_fs[read, write, edit, create_dir, move, allowed], // Execute Ω₅: Φ_fs[read, read_multi, list, tree, search, info, allowed] // Review }
🔒 Filesystem Permission Matrix
ℙΦ = { Ω₁: {read: ✓, create: ✗, update: ✗, delete: ✗}, // Research Ω₂: {read: ✓, create: ~, update: ✗, delete: ✗}, // Innovate Ω₃: {read: ✓, create: ✓, update: ~, delete: ✗}, // Plan Ω₄: {read: ✓, create: ✓, update: ✓, delete: ~}, // Execute Ω₅: {read: ✓, create: ✗, update: ✗, delete: ✗} // Review }
🔍 Filesystem Operation Categories
𝕆fs_read = {read, read_multi, list, tree, search, info, allowed} 𝕆fs_create = {write, create_dir} 𝕆fs_update = {edit, move} 𝕆fs_delete = {delete} // Not directly exposed in basic MCP
📡 Filesystem Context Integration
// Add Filesystem to Context References Γ₉ = 🗃️ @Filesystem
// Update Mode-Context Mapping to include Filesystem MΓ_fs = { Ω₁: MΓ[Ω₁] + [Γ₉], // Add to Research Ω₂: MΓ[Ω₂], // Innovate unchanged Ω₃: MΓ[Ω₃] + [Γ₉], // Add to Plan Ω₄: MΓ[Ω₄] + [Γ₉], // Add to Execute Ω₅: MΓ[Ω₅] + [Γ₉] // Add to Review }
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 · 171 lines · 1,699 tokens per session scan A 744725f78124
mcp-filesystem 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,699 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
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.