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/rustkit-ai/aimemoWrote 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/rustkit-ai/aimemo/aimemo)<a href="https://agentmods.dev/rules/rustkit-ai/aimemo/aimemo"><img src="https://agentmods.dev/badge/rules/rustkit-ai/aimemo/aimemo/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/rustkit-ai/aimemo/aimemo"><img src="https://agentmods.dev/badge/rules/rustkit-ai/aimemo/aimemo.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.00075 | $0.00075 |
| Opus 5.5 | $0.00030 | $0.00030 |
| Sonnet 5.5 | $0.00015 | $0.00015 |
| Haiku 4.5 | $0.00007 | $0.00007 |
Grade A, and why
aimemo 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
aimemo — persistent memory
- Run
aimemo injectat the start of every session to recall context - Run
aimemo log "<what you did>"after each significant task - Run
aimemo log "todo: <next step>"before ending the session
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 · 10 lines · 75 tokens per session scan A 77b8ba994bbb
aimemo is a cursor rule published in the GitHub repository rustkit-ai/aimemo (4 stars, last pushed 7mo ago), licensed MIT. It adds 75 tokens to every session, about $0.0003 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
haive-memories
Hivelore shared memories & block sensors (auto-generated).
haive-mcp-required
Require Hivelore MCP (getbriefing / memrelevantto) before substantive repo edits.
swamr-obsidian-brain
Swamr Obsidian Brain — persistent knowledge base that agents read from and write to across phases. Prevents context loss by maintaining architecture decisions, task outputs, learned patterns, and project knowledge in an Obsidian vault. Every agent MUST read relevant notes before starting and write a summary note when…
read-xlsx
Reading, writing, diffing, and repairing spreadsheets (.xlsx) for AI agents via the xfa MCP server.
cursor
Cursor rule "cursor" from nitingupta220/riperflow, covering riperflow σ and ω₁=🔍r→ℙ(ω₁)→research.
shared-agents-knowledge
Shared agents skills and learnings — automatic sync, retrieve, capture.