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/Jkudjo/oh-my-cursorWrote 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/jkudjo/oh-my-cursor/note)<a href="https://agentmods.dev/rules/jkudjo/oh-my-cursor/note"><img src="https://agentmods.dev/badge/rules/jkudjo/oh-my-cursor/note/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/jkudjo/oh-my-cursor/note"><img src="https://agentmods.dev/badge/rules/jkudjo/oh-my-cursor/note.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.00014 | $0.00237 |
| Opus 5.5 | $0.00006 | $0.00095 |
| Sonnet 5.5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
note 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
@note
Trigger: When you want to capture a decision, observation, or thought mid-session.
Protocol
- Parse the note content from the argument.
- Generate a key from the content (e.g. "decision-auth-jwt", "observation-perf-bottleneck").
- Prepend timestamp:
[{ISO date}] {content}. - Call
set_memorykey=note-{generated-key}, value=the timestamped note. - Confirm: "Note saved: {key}"
Examples
@note "decided to use JWT over sessions — simpler for stateless API"
@note "perf bottleneck is in the query on line 47 of user-service.ts"
@note "TODO: revisit the error handling in auth middleware after shipping"
Rules
- Short notes only — for long-form content use
save_artifact. - Notes accumulate — they are not overwritten by default.
- Use
omc memory listto review all notes later.
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 First seen · 32 lines · 14 tokens per session scan A 251c6eb9b94e
note is a cursor rule published in the GitHub repository Jkudjo/oh-my-cursor (1 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 237 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
100-memory-system
Comprehensive Memory System architecture for autonomous Cursor operation.
memory-bank
You are an expert software engineer with a unique characteristic: your memory resets completely between sessions. This isn't a limitation - it's what drives you to maintain perfect documentation. At the beginning of each dialogue, you rely ENTIRELY on your Memory Bank to understand the project and continue work…
memory-protocol
A protocol for storing and retrieving project memories from files, using a command-line memory tool. It records decisions, preferences, dates, tasks, and other useful history for later conversations.
context-prime
Prime Claude with comprehensive project understanding.
cognitive-principle-check
A consistency check for adding new material to L1 cognitive-structure documents. It compares the new text with confirmed L1.5 principles, which are the system’s underlying rules.
create-rule-agent
This rule is responsible for creating and updating Cursor rules. Cursor rules govern the structure, hierarchy, style and organization of code in a project. This rule should be invoked in Agent mode when: 1. a user wants to create a new cursor rule, 2. a user wants to update or change an existing rule, 3. user wants…