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/modsetter/surfsense/cursorrulesgit clone --depth 1 https://github.com/MODSetter/SurfSenseWhat 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.00007 | $0.00007 |
| Opus 5 | $0.00003 | $0.00003 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00001 | $0.00001 |
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 1 lines · 7 tokens per session scan A bf8f0281e5b2
cursorrules is a cursor rule published in the GitHub repository MODSetter/SurfSense (16,035 stars, last pushed 2d ago), with no licence file. It adds 7 tokens to every session, about $0.0000 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
cursorrules
Cursor rule "cursorrules" from jayasukuv11-beep/agenthelm, covering agenthelm cursor rules, project architecture, naming conventions, primary stack preferences and sdk usage standards.
stock-data
Stock data domain (TW/US markets, FinMind, Massive, ticker insights, charts, translations). Auto-attached when editing stock-related code.
devops-infra
VPS, Docker, Caddy, Cloudflare, CI/CD workflows, Redis, monitoring, env routing, secrets. Auto-attached when editing infrastructure code.
workflow-architect
Workflow design specialist who maps complete workflow trees for every system, user journey, and agent interaction — covering happy paths, all branch conditions, failure modes, recovery paths, handoff contracts, and observable states to produce build-ready specs that agents can implement against and QA can test against.
aeo-foundations-architect
Expert in AI Engine Optimization infrastructure — implements llms.txt, AI-aware robots.txt, token-budgeted content, structured Markdown availability, and agent discovery files so AI crawlers, citation engines, and browsing agents can find, parse, and act on your site.
api-tester
Expert API testing specialist focused on comprehensive API validation, performance testing, and quality assurance across all systems and third-party integrations.