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/mashware/domain-memory/cursorgit clone --depth 1 https://github.com/mashware/domain-memoryWhat 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.00221 | $0.00221 |
| Opus 5 | $0.00111 | $0.00111 |
| Sonnet 5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
cursor 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
Domain Memory
This project uses domain-memory to accumulate business-domain knowledge (flows, decisions, integrations, "why" nuances).
Read the full instructions at .domain-memory/instructions.md at the start of every session. They are mandatory and cover when to query the MCP, how to use per-branch staging, the "why vs what" rule, conflict handling, and the PR flow.
Minimum rules if you have not yet read the full instructions:
- On startup, query the
domain-memoryMCP withsearch_knowledgeusing the current task. If it fails or takes >2s, continue without context. - Silence by default: do not propose saving knowledge unless there is a strong signal.
- Before writing to the store, always re-query. Never trust what you remember from the start of the session.
- Conflicts block the save and are resolved live with the user.
- MCP failures must never break the session or surface as an unsolicited error to the user.
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 · 18 lines · 221 tokens per session scan A 686b98534e9a
cursor is a cursor rule published in the GitHub repository mashware/domain-memory (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 221 tokens to every session, about $0.0011 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
pytest-integration-tests
Below is an example test. Notice the following.
python-app
Cursor rule "python-app" from iloveitaly/llm-ide-rules, covering python app, factories and database & orm.
react
Cursor rule "react" from iloveitaly/llm-ide-rules, covering react, mock data, react hook form and styling.
alembic-migrations
To add a non-nullable column and set a specific value for all existing rows without a persistent server default.
read-xlsx
Reading, writing, diffing, and repairing spreadsheets (.xlsx) for AI agents via the xfa MCP server.
cursorrules
═══════════════════════════════════════════════════════════ SPEC DRIVEN DEVELOPMENT — PROJECT CONSTITUTION Project: Freelance Time Tracker Version: v1.0.