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/sandraschi/tailscale-mcp/cursorrulesgit clone --depth 1 https://github.com/sandraschi/tailscale-mcpWhat 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.00703 | $0.00703 |
| Opus 5 | $0.00351 | $0.00351 |
| Sonnet 5 | $0.00141 | $0.00141 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
cursorrules 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 yesterday.
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.
This is a copy
83% identical to cursorrules — 23 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Central Documentation Rules
Rule #1: Read Central Docs First
BEFORE making any changes or starting work, ALWAYS:
-
Read the Central Documentation README:
- Location:
D:\Dev\repos\mcp-central-docs\README.md - This shows all important documentation "branches" (folder trees)
- Navigate from there to find specific information
- Location:
-
Follow Documentation Branches:
- Central docs are organized by topic (Anthropic ecosystem, Google ecosystem, patterns, projects, etc.)
- Each branch has its own README explaining what's inside
- Use the branch structure to find relevant docs
-
Check for Existing Patterns:
- Look in
docs/patterns/for design patterns - Check
templates/for reusable templates - Review
docs/projects/for similar project examples
- Look in
-
Avoid Duplication:
- Search existing docs before creating new ones
- Update existing docs rather than creating duplicates
- Reference central docs instead of copying content
Documentation Branches (from Central README)
Core Standards
STANDARDS.md- Documentation quality standardsSTRUCTURE.md- Directory layout guideCONTRIBUTING.md- How to contribute
Anthropic Ecosystem (docs/anthropic-ecosystem/)
- MCP Protocol, FastMCP, MCPB, Claude Desktop, Glama
Google Ecosystem (docs/google-ecosystem/)
- Gemini 3, Antigravity IDE, Nano Banana Pro, DeepMind, TPU infrastructure
Patterns (docs/patterns/)
- Design patterns for MCP servers and development
Projects (docs/projects/)
- myai, veogen, mywienerlinien, autohotkey
Monitoring (monitoring/)
- Prometheus/Grafana/Loki stack
Templates (templates/)
- Reusable templates and scripts
Quick Reference
Central Docs Location: D:\Dev\repos\mcp-central-docs\
Start Here: D:\Dev\repos\mcp-central-docs\README.md
When in doubt: Read the central README and navigate from there.
Session Context (Tailscale MCP)
You have access to a Tailscale network controller with 24 tools spanning device management, DNS, Funnel, Taildrop, security, monitoring, and LM Link (Tailscale + LM Studio encrypted remote LLM mesh).
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.
- yesterday First seen · 86 lines · 703 tokens per session scan A 92f1c8b0c8b4
cursorrules is a cursor rule published in the GitHub repository sandraschi/tailscale-mcp (4 stars, last pushed 16d ago), licensed MIT. It adds 703 tokens to every session, about $0.0035 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to cursorrules, differing in 23 lines, and is treated as a copy.
Other cursor rules, from other repositories
cursorrules
BEFORE making any changes or starting work, ALWAYS.
cursorrules
Composite MCP server for AI-powered music production workflows. Mounts and orchestrates multiple MCP servers (VirtualDJ, Plex, Suno, Reaper, OBS).
cursorrules
You have access to an MCP server that automates Notepad++ on Windows: fileops, textops, tabops, sessionops, lintingops, displayops, pluginops, statusops (portmanteau tools with an operation enum).
cursorrules
FastMCP server + webapp that bridges Claude Desktop / Cursor to OpenClaw (agent Gateway, channels, routing, sessions, skills, security) and Moltbook (AI-agent social network). It uses those platforms; it does not implement or replace them.
cursorrules
You can control Streamfog AR lenses, face filters, and Vtuber avatars on the live OBS stream via the Streamer.bot bridge (5 MCP tools: streamfogstatus, streamfogsetlens, streamfogcleareffects, streamfogtoggleavatar, streamfoglistlenses).
cursorrules
You have access to a Discord bot bridge with 36 operations via a portmanteau tool, LanceDB RAG, and agentic workflows.