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/knaisoma/data-olympus/cursorrulesgit clone --depth 1 https://github.com/knaisoma/data-olympusWhat 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.00103 | $0.00103 |
| Opus 5 | $0.00051 | $0.00051 |
| Sonnet 5 | $0.00021 | $0.00021 |
| Haiku 4.5 | $0.00010 | $0.00010 |
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 2d 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
Always write tests before implementation code. Every feature and bugfix must be covered by a test that fails before the change and passes after it. Keep the test suite fast and deterministic.
Prefer composition over inheritance when structuring modules. Small focused functions are easier to test and reason about than deep class hierarchies. Avoid global mutable state in the request path.
Use type hints on every public function. Run the type checker in CI and treat type errors as build failures rather than warnings.
x
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.
- 2d ago First seen · 13 lines · 103 tokens per session scan A f779485481c2
cursorrules is a cursor rule published in the GitHub repository knaisoma/data-olympus (23 stars, last pushed 21d ago), licensed Apache-2.0. It adds 103 tokens to every session, about $0.0005 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
cursorrules
This project uses Spectra for Spec-Driven Development(SDD).
llm-wiki-quality
Quality checks for synthesized wiki content.
about-this-repo
このリポジトリの背景・概要・目的（OCD MCP プロジェクトコンテキスト）.
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.