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/rizvee/multimodel-dev-os/cursorrulesgit clone --depth 1 https://github.com/rizvee/multimodel-dev-osWhat 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.00207 | $0.00207 |
| Opus 5 | $0.00103 | $0.00103 |
| Sonnet 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 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
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.
- yesterday 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 15d ago), licensed MIT. It adds 207 tokens to every session, about $0.0010 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
020-agent-skill-authoring
Authoring agent, skill, and command markdown for cross-harness portability.
000-project-conventions
This is a multi-harness plugin marketplace. Source lives under plugins/; per-harness artifacts (.codex/, .cursor-plugin/, .opencode/, commands/) are generated.
010-python-tooling
Python tooling and dependency conventions for plugin-eval and tools/.
050-plan
When the user types /plan or asks to create a project plan, feature PRD, or retrospective.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.