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/shahrukh-hack/vibe-memory/cursorrulesgit clone --depth 1 https://github.com/shahrukh-hack/vibe-memoryWhat 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.00077 | $0.00077 |
| Opus 5 | $0.00039 | $0.00039 |
| Sonnet 5 | $0.00015 | $0.00015 |
| Haiku 4.5 | $0.00008 | $0.00008 |
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 today.
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.
- today First seen · 7 lines · 77 tokens per session scan A 294c8f17df49
cursorrules is a cursor rule published in the GitHub repository shahrukh-hack/vibe-memory (0 stars, last pushed 12d ago), with no licence file. It adds 77 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
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
react-best-practices
USE WHEN: Designing React components, implementing hooks, and managing component lifecycles.
performance
USE WHEN: Optimizing Core Web Vitals, managing assets, and ensuring high Lighthouse/A11y scores.
testing
USE WHEN: Writing unit, integration, or component tests. Mandatory for logic in features.
marker-triage
Triage a Marker.io website-feedback backlog at scale. Use when asked to go through, categorize, prioritize, deduplicate, or make sense of many Marker.io issues at once. Splits content fixes from functional bugs, groups by page, rates criticality, flags duplicates and repeat reporters, surfaces quick wins, lists…
marker-insights
Aggregate Marker.io website feedback into recurring patterns. Use when asked to find the most common issues on a site, which pages get the most feedback, recurring content problems, or the content-vs-bug split across many Marker.io reports, and produce a prioritized brief for a website team or agency. Read-only: it…