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/safedep/vet/cursorrulesgit clone --depth 1 https://github.com/safedep/vetWhat 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.00008 | $0.00008 |
| Opus 5 | $0.00004 | $0.00004 |
| Sonnet 5 | $0.00002 | $0.00002 |
| 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.
What it actually says
Always use TypeScript for new files.
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 · 2 lines · 8 tokens per session scan A fb59274e7e2f
cursorrules is a cursor rule published in the GitHub repository safedep/vet (1,103 stars, last pushed 5d ago), licensed Apache-2.0. It adds 8 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
adapter-features
Database-specific features must be implemented in the specialized adapter only. Base adapters (postgres, mysql, etc.) must remain database-agnostic.
unit-tests-tdd
TDD required for behavior changes; ≥80% package coverage on touched packages; unit-test conventions.
cursorrules
aggregatereports to keep SUMMARY.md and metadata.json synchronized.
refactor-large-files
Guidance for splitting large route files into maintainable pieces.
seed-data
Patterns for development seed data — stable UUIDs, realistic data, cross-references.
feature-flags
Feature flag patterns — use when working with feature toggles.