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.
git clone --depth 1 https://github.com/goranocokoljic/pure-contextWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/goranocokoljic/pure-context/purecontext)<a href="https://agentmods.dev/rules/goranocokoljic/pure-context/purecontext"><img src="https://agentmods.dev/badge/rules/goranocokoljic/pure-context/purecontext/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/goranocokoljic/pure-context/purecontext"><img src="https://agentmods.dev/badge/rules/goranocokoljic/pure-context/purecontext.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00667 | $0.00667 |
| Opus 5.5 | $0.00267 | $0.00267 |
| Sonnet 5.5 | $0.00133 | $0.00133 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
purecontext 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hmmm--- description: PureContext MCP code navigation rules alwaysApply: true
PureContext MCP — Code Navigation
Always use PureContext MCP tools for code navigation. Never read entire files to find code.
Mandatory workflow
- Start every session:
list_repos()→ getrepoId(required for all tools) - Find code by name:
search_symbols→ readsummaryandsignature→ only callget_symbol_sourcefor symbols you will actually edit - Find code by behaviour:
search_semanticfor conceptual queries;search_textfor literals/comments
Pick the right tool
| I need to… | Use |
|---|---|
| Find a function/class/method by name | search_symbols |
| Find code by what it does (meaning) | search_semantic |
| Find a literal string, comment, or config value | search_text |
| Read a symbol's implementation | get_symbol_source |
| Read a non-symbol file region (imports, config) | get_file_content |
| Survey one file / the whole project | get_file_outline / get_repo_outline |
| Know what breaks if I change a symbol | get_blast_radius |
| Find every call site of a symbol | find_references |
| See the callers/callees tree | get_call_hierarchy |
| Judge how risky a symbol is to change | get_symbol_risk |
| Find files that change together with this one | get_co_change |
| Pre-flight a rename / delete / move | check_rename_safe / check_delete_safe / check_move_safe |
| Find exported symbols with no tests | find_untested_symbols |
| Codebase health score / debt report | health_radar / get_debt_report |
Before editing risky code
Before broad or automated edits to an unfamiliar symbol, check get_symbol_risk (composite churn + centrality + complexity + test-gap + co-change, banded low/review/high). For a high symbol, inspect its callers (get_blast_radius) and its historical co-changers (get_co_change) first — co-changing files are the second-order edits the import graph can't show you. search_symbols and get_symbol_source accept includeRisk: true to attach a compact { band, riskScore } inline.
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.
- 2mo ago First seen · 48 lines · 667 tokens per session scan A df436e39c466
purecontext is a cursor rule published in the GitHub repository goranocokoljic/pure-context (7 stars, last pushed 5d ago), licensed MIT. It adds 667 tokens to every session, about $0.0027 per session on Opus 5.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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.