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/projas01/sp-devcontrol/cursorrulesgit clone --depth 1 https://github.com/PRojas01/SP-DevControlWhat 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.00075 | $0.00075 |
| Opus 5 | $0.00037 | $0.00037 |
| Sonnet 5 | $0.00015 | $0.00015 |
| Haiku 4.5 | $0.00007 | $0.00007 |
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.
What it actually says
SP-DevControl — Cursor Rules (SP-DevControl)
RULES:
- Never delete files. Use .v2 suffix
- Present plan before modifying >3 files
- Stay in: src/, scripts/, tests/, lib/, docs/
- Protected: dist/, .env, .devcontrol/, *.lock, node_modules/
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 · 20 lines · 75 tokens per session scan A 8137828679cf
cursorrules is a cursor rule published in the GitHub repository PRojas01/SP-DevControl (0 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session, about $0.0004 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-31.
Other cursor rules, from other repositories
pytest-integration-tests
Below is an example test. Notice the following.
python-app
Cursor rule "python-app" from iloveitaly/llm-ide-rules, covering python app, factories and database & orm.
alembic-migrations
To add a non-nullable column and set a specific value for all existing rows without a persistent server default.
read-xlsx
Reading, writing, diffing, and repairing spreadsheets (.xlsx) for AI agents via the xfa MCP server.
cursorrules
═══════════════════════════════════════════════════════════ SPEC DRIVEN DEVELOPMENT — PROJECT CONSTITUTION Project: Freelance Time Tracker Version: v1.0.
cursorrules
When the user asks about COBOL, legacy modernization, mainframe migration, banking IT, COBOL parser, use cobol-bridge-mcp tools.