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/AG-Dmitry/composer-enhancedWrote 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/ag-dmitry/composer-enhanced/02-context-grounding)<a href="https://agentmods.dev/rules/ag-dmitry/composer-enhanced/02-context-grounding"><img src="https://agentmods.dev/badge/rules/ag-dmitry/composer-enhanced/02-context-grounding/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/ag-dmitry/composer-enhanced/02-context-grounding"><img src="https://agentmods.dev/badge/rules/ag-dmitry/composer-enhanced/02-context-grounding.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.00024 | $0.00577 |
| Opus 5.5 | $0.00010 | $0.00231 |
| Sonnet 5.5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
02-context-grounding 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 2 — Context Grounding
Persona: Planner. No code in this phase.
Cheap models hallucinate APIs, import paths, and file contents. This phase replaces guessing with evidence.
The anti-assumption rule
If you have not read it, you do not know it. Anything unverified is an assumption, and assumptions must be checked or asked — never coded against.
Steps
-
Read the files you will touch, fully enough to understand them. Never edit a file you have not read in this session.
-
Verify every external reference you intend to use actually exists:
- Functions / hooks / components — confirm the real signature, not a guessed one.
- Import paths and module exports — confirm they resolve.
- Types and fields — confirm they exist with the names/shapes you expect. Use search/read tools. Do not rely on memory of "how this library usually works".
-
Trace the data flow / call sites relevant to the change, so you know what you might break.
-
Keep context high-signal (avoid context rot). Read widely to find the relevant slice, but keep only high-signal context in view — a cheap model's attention degrades and cost rises when the window fills with irrelevant tokens. For broad exploration, prefer a readonly explore subagent so only its digest enters your context (see
escalation-subagents.mdc). -
Find existing patterns to reuse. Prefer the codebase's existing helpers, conventions, and abstractions over inventing new ones. Check whether a dependency or utility already exists before adding one.
-
Consult project docs/rules for the area you are touching. See
project-adapter.mdcfor which docs and rules apply.
Working memory
Fill the File ledger section of the task-memory file: for each relevant
file, record path -> one-line summary + the line ranges that matter. This lets
you avoid re-reading unchanged files later (drift is detected via git — see
working-memory.mdc).
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 · 60 lines · 24 tokens per session scan A 6c7b8cd84812
02-context-grounding is a cursor rule published in the GitHub repository AG-Dmitry/composer-enhanced (3 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 577 once invoked, about $0.0001 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
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.