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/kingemma7/cursor-os/coregit clone --depth 1 https://github.com/KingEmma7/cursor-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.00232 | $0.00232 |
| Opus 5 | $0.00116 | $0.00116 |
| Sonnet 5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
core 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
The engineering contract for this repo lives in AGENTS.md (auto-loaded). Follow it. This rule only adds Cursor-specific behavior so the contract is not duplicated token-for-token on every request.
- Consult project memory before non-trivial work:
docs/repo-memory.md(durable facts),docs/decision-log.md(past decisions). Don't contradict a logged decision without flagging it. - When project-specific docs conflict, prefer the newest explicit decision in
docs/decision-log.md, then update stale docs. - For multi-file, risky, or ambiguous changes, use Plan mode (or write a short plan) and get alignment before editing.
- Gate completion on
docs/quality-rubric.md. Don't claim done until its checks pass with evidence. - Keep memory current: when you learn a durable fact or make a notable decision, update
docs/repo-memory.mdor append todocs/decision-log.md. - If a rule, doc, or
AGENTS.mdclaim is stale or wrong, fix it as part of your change instead of working around it.
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 · 13 lines · 232 tokens per session scan A eb8f537af1e9
core is a cursor rule published in the GitHub repository KingEmma7/cursor-os (2 stars, last pushed 20d ago), licensed MIT. It adds 232 tokens to every session, about $0.0012 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
project
Project conventions - canonical source is AGENTS.md.
react
React component conventions.
react
React component conventions.
cadence-nft-standards
Comprehensive standards and best practices for developing Non-Fungible Tokens (NFTs) using Cadence. Ensures proper implementation of NonFungibleToken interfaces, MetadataViews integration for marketplace compatibility, secure resource handling patterns, and advanced modular architectures for complex NFTs with traits…
flow-configuration
Comprehensive guide to Flow project configuration covering flow.json structure, CLI workflow, FCL integration, network management, and deployment best practices. Covers contract aliases, account management, dependency resolution, frontend FCL setup with React SDK, and environment-based configuration for seamless…
flow-development-workflow
Streamlined Flow development workflow covering documentation-first debugging methodology, iterative development approach, deployment verification, gas optimization strategies, and comprehensive testnet validation protocols. Focuses on practical workflows and error prevention rather than configuration details.