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/yanqiw/comemWrote 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/yanqiw/comem/cursor)<a href="https://agentmods.dev/rules/yanqiw/comem/cursor"><img src="https://agentmods.dev/badge/rules/yanqiw/comem/cursor/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/yanqiw/comem/cursor"><img src="https://agentmods.dev/badge/rules/yanqiw/comem/cursor.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.00434 | $0.00434 |
| Opus 5.5 | $0.00174 | $0.00174 |
| Sonnet 5.5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00043 | $0.00043 |
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 1mo 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.
What it actually says
Follow the Coordination Memory protocol in AGENTS.md (the section between the
coordination-memory markers).
completed_gate_passedis not accepted truth — only an integratoraccept_eventmakes work accepted.- Claim assignments before working; carry the current
base_revisionon mutating calls. - Discover with
list_workspaces, then useget_workspace_detail(workspace_id) for compact teams and assignment counts. Choose one team and pass its requiredteam_idtoget_team_board,list_pending_reviews,get_snapshot,list_contracts, andget_attention_boardbefore high-volume reads; there is no pagination. - Use
get_event_detail,get_assignment_detail,get_run_detail, orget_contract_detailonly after choosing a specific ID from a compact read. get_team_boardreturns onlyassignment_id,title, andstatus.get_team_board.statusis an optional, one exact status filter; omitting it excludesaccepted,rejected,cancelled, andsuperseded. Callget_assignment_detailfor the full task contract.- Only these eleven Ack tools return a compact acknowledgement without a
payload echo:
append_event,submit_handoff,heartbeat_run,checkpoint_run,raise_attention,record_run_binding,request_intervention,respond_intervention,review_event,accept_event, andreject_event. claim_assignmentand actor/workspace/team/assignment/contract mutations retain their existing responses; keep usingactive_run_idfromclaim_assignment.- For loop-dispatched work, read
metadata.context_refs, obeyallowed_pathsandacceptance_criteria, usemetadata.session_bind.target_actor_idas the intended worker binding before any run exists, and keep run communication metadata current withrecord_run_binding.
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.
- 1mo ago Changed · +17 lines · +272 tokens per session f6ed9f2e8e72
- 1mo ago First seen · 18 lines · 162 tokens per session scan A af180a556dc6
cursor is a cursor rule published in the GitHub repository yanqiw/comem (1 stars, last pushed 1mo ago), licensed MIT. It adds 434 tokens to every session, about $0.0017 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
context-discipline
Manage AI context window efficiently - read before write, no re-reads, tool-call budgets, one-pass discipline.
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
jarvis-agent-rules
MCP server jarvis: notes, Jira, knowledge graph, sessions, preferences.
alaya-agent-working-contract
Alaya working contract — goal, honesty, modes, review loops, worktrees (fills do-it gaps).
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.