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.
git clone --depth 1 https://github.com/rizvee/multimodel-dev-osWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/rizvee/multimodel-dev-os/cursorrules)<a href="https://agentmods.dev/rules/rizvee/multimodel-dev-os/cursorrules"><img src="https://agentmods.dev/badge/rules/rizvee/multimodel-dev-os/cursorrules/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/rizvee/multimodel-dev-os/cursorrules"><img src="https://agentmods.dev/badge/rules/rizvee/multimodel-dev-os/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00207 | $0.00207 |
| Opus 5.5 | $0.00083 | $0.00083 |
| Sonnet 5.5 | $0.00041 | $0.00041 |
| Haiku 4.5 | $0.00021 | $0.00021 |
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 1mo ago.
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
AUTO-GENERATED REFERENCE — Source of truth: /AGENTS.md
Do not edit this file directly. Edit /AGENTS.md and re-sync.
Cursor Rules for multimodel-dev-os project
Full instructions: /AGENTS.md
Project Overview
project: null
stack: null
Build Commands
dev: null
build: null
test: null
lint: null
Coding Conventions
- See /AGENTS.md for full style guide
- See /MEMORY.md for project-specific patterns
Boundaries — do not modify
- .env, .env.local
- node_modules/
- package-lock.json
Agent Behavior
- Check /TASKS.md before starting work
- Update /MEMORY.md with decisions made
- Follow /RUNBOOK.md for deploy procedures
- Log sessions to .ai/session-logs/ when handing off to another tool
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.
- 1mo ago First seen · 31 lines · 207 tokens per session scan A 2992a7e188cd
cursorrules is a cursor rule published in the GitHub repository rizvee/multimodel-dev-os (5 stars, last pushed 5d ago), licensed MIT. It adds 207 tokens to every session, about $0.0008 per session on Opus 5.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
memory-bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…
code-quality
Code quality standards for all code changes.
review-gate
Pre-delivery review checklist — run before committing or delivering code.
ai-security
Security best practices for LLM/AI applications - prompt injection defense, rate limiting, PII protection.
unity-input
Guidelines for working with the New Input System in Unity 6.2.
unity-ui
Assets/ ├── UI/ │ ├── Runtime/ │ │ ├── Controllers/ │ │ │ └── MainMenuController.cs │ │ ├── Views/ │ │ │ └── MainMenuView.cs │ │ ├── ViewModels/ │ │ │ └── HealthViewModel.cs │ │ ├── UXML/ │ │ │ └── MainMenu.uxml │ │ └── USS/ │ │ └── MainMenu.uss │ └── Editor/ │ └── UIBuilderExtensions.cs.