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/cote-star/agent-chorus/cursorrulesgit clone --depth 1 https://github.com/cote-star/agent-chorusWhat 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.00074 | $0.00074 |
| Opus 5 | $0.00037 | $0.00037 |
| Sonnet 5 | $0.00015 | $0.00015 |
| Haiku 4.5 | $0.00007 | $0.00007 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cursorrules — 100% identical, 0 lines differ
What it actually says
- Read .agent-context/current/routes.json to identify task type
- Load contracts from .agent-context/current/completeness_contract.json + .agent-context/current/search_scope.json
- Search ONLY within scoped directories defined in search_scope.json
- Do not open repo source files before step 3
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 · 7 lines · 74 tokens per session scan A d6c094db351a
cursorrules is a cursor rule published in the GitHub repository cote-star/agent-chorus (13 stars, last pushed 2mo ago), licensed MIT. It adds 74 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-30.
Other cursor rules, from other repositories
verify-ai-readiness
Holistic assessment of the AI knowledge layer on a 5-level maturity scale; flags agent-blocking gaps.
03-skill-testcases
SKILL: Generate Test Scenarios Matrix from API spec (use for /api-isolated-tests).
01-qa-agent
QA AGENT PERSONA: Principles, Anti-patterns, workflows.
karpathy-guardrails
Karpathy coding guardrails — think first, simplicity, surgical changes, goal-driven.
ai-dev-os-review
Performs a comprehensive self-review before creating a PR. Combines guideline compliance checking (L3) with design-level review (L2) and philosophical alignment (L1). Unlike @ai-dev-os-check which only checks rules, this also evaluates architecture decisions and code design quality.
cursorrules
ALWAYS start your session by reading AGENTS.md and .memory/wiki/hot.md to get project context before suggesting code or answering questions.