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/ogro-projukti/codegenome/cursor-rulesgit clone --depth 1 https://github.com/Ogro-Projukti/codegenomeWhat 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.00554 | $0.00554 |
| Opus 5 | $0.00277 | $0.00277 |
| Sonnet 5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
cursor-rules 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.
This is a copy
94% identical to codegenome-knowledge-graph — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeGenome MCP Integration
You are operating within a repository analyzed by CodeGenome, an architectural knowledge graph tool. This project contains a .genome/ directory.
Core Directives
- Mandatory MCP Usage: When
.genome/codegenome.dbexists, you MUST use CodeGenome MCP access for all codebase, architecture, dependency, or symbol queries whenever it is available. - Access Order: First use native CodeGenome MCP tools exposed in your context. If those tools are missing, you MAY try a local MCP HTTP endpoint such as
http://127.0.0.1:{{MCP_PORT}}/mcpwhen the user has started it or configured it. Treat this as MCP transport access, not as an arbitrary application HTTP API. - Prefer Graph over Grep: Use graph-backed MCP tools instead of raw file searching (
grep) or reading entire files blindly. The graph provides semantic understanding. - Fallback Gracefully: If native MCP tools are missing and HTTP MCP access is unavailable, incompatible, or returns empty data, tell the user exactly what failed and what to configure. Then, if needed, read
.genome/graph.jsonor.genome/exports/*.mdbefore resorting to standard text searches. - Keep Context Fresh: After modifying code files, remind the user to run
codegenome analyzeor start the live evolution servercodegenome evolve --liveto keep the graph updated.
Available MCP Capabilities
- Discovery:
search_nodes(find symbols) - Relationships:
get_neighbors(imports, callers, callees) - Architecture:
get_entry_points,get_dead_code,get_circular_deps,get_god_nodes - Metrics:
get_complexity,get_churn,get_graph(summary statistics) - Evolution:
get_timeline,get_changes(architectural diffs)
Constraints & Behaviors
- Only read
.genome/graph.jsonor.genome/exports/*.mddirectly if native MCP tools and local HTTP MCP transport are unavailable or fail to surface enough context. - Verify your MCP usage by monitoring tool call success. If native tools are missing, try the configured local HTTP MCP endpoint when possible. If both native and HTTP MCP access fail, politely ask the user to configure their editor's MCP settings to run
codegenome mcp-start(stdio) or start the server withcodegenome mcp-start --transport http.
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 · 30 lines · 554 tokens per session scan A 3ffe193de7df
cursor-rules is a cursor rule published in the GitHub repository Ogro-Projukti/codegenome (23 stars, last pushed 1mo ago), licensed MIT. It adds 554 tokens to every session, about $0.0028 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to codegenome-knowledge-graph, differing in 2 lines, and is treated as a copy.
Other cursor rules, from other repositories
04-spatial-parser
Guidelines for Spatial RAG and Markdown parsing.
02-python-standards
Python coding standards, libraries, and concurrency safety.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.