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/codesteward/codesteward-graph/cursorrulesgit clone --depth 1 https://github.com/Codesteward/codesteward-graphWhat 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.00403 | $0.00403 |
| Opus 5 | $0.00201 | $0.00201 |
| Sonnet 5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00040 | $0.00040 |
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
Codesteward Graph — Code Intelligence
This project has the Codesteward MCP graph server connected. It has already parsed this codebase into a structural graph.
Prefer graph tools over file reads for structural questions
For questions about code structure, relationships, and dependencies, use the graph tools first. They answer cross-file, cross-language questions in a single call that would otherwise require reading and grepping many files.
Use graph tools for:
- Finding functions, classes, or methods by name → codebase_graph_query (lexical)
- Finding what calls a function, or what a function calls → codebase_graph_query (referential)
- Checking whether a route is protected by auth middleware → codebase_graph_query (referential, filter on GUARDED_BY/PROTECTED_BY)
- Listing external package dependencies → codebase_graph_query (dependency)
- Tracing data flow → codebase_graph_query (semantic)
Use file reads when you need the actual source code of a specific function or file after identifying it via the graph.
Workflow
Before your first structural query in a session, check if the graph is ready:
graph_status()
If last_build is null or the graph looks stale after recent changes:
graph_rebuild()
No arguments needed — the server already knows the repo path.
Then query:
codebase_graph_query(query_type="referential", query="authenticate")
query_type reference
- lexical → find functions/classes/methods by name or file
- referential → find call/import/extends/auth-guard relationships
- semantic → trace data-flow relationships
- dependency → list external package dependencies
- cypher → custom Cypher query for anything not covered above
Recording inferred relationships
If you identify a relationship through reasoning that the parser could not detect (e.g. a dynamic call or runtime-resolved dependency), record it with graph_augment. Use node_id values from query results as source_id and target_id.
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 · 51 lines · 403 tokens per session scan A 431d2741eb06
cursorrules is a cursor rule published in the GitHub repository Codesteward/codesteward-graph (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 403 tokens to every session, about $0.0020 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
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
java-springboot-jpa-cursorrules-prompt-file
description: "Cursor rules for Java development with Springboot and JPA integration." globs: / alwaysApply: false.
002-verify-before-act
Requires Claude to read before writing, verify before installing, and confirm before destructive operations.
swift-development
Swift development: SwiftUI, Combine, async/await, iOS patterns, and Apple platform conventions.
design-patterns
Design patterns (GoF) and file size conventions for sweagent TypeScript codebase.
database
Cursor rule "database" from ItamarZand88/awesome-agent-conventions, covering database best practices, prisma setup, prisma models, prisma queries and supabase setup.