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/thinhledev/mixaiWrote 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/thinhledev/mixai/mixai-memory)<a href="https://agentmods.dev/rules/thinhledev/mixai/mixai-memory"><img src="https://agentmods.dev/badge/rules/thinhledev/mixai/mixai-memory/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/thinhledev/mixai/mixai-memory"><img src="https://agentmods.dev/badge/rules/thinhledev/mixai/mixai-memory.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.00268 | $0.00268 |
| Opus 5.5 | $0.00107 | $0.00107 |
| Sonnet 5.5 | $0.00054 | $0.00054 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
mixai-memory 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
Mixai project memory
This project has persistent local memory managed by mixai. Before re-exploring the repository from scratch, check it first: use the memory_search MCP tool or mixai memory search "<topic>" for past decisions, constraints, and outcomes (results are compact previews — drill in with memory_get or mixai memory show <id>). Record new durable decisions the moment they are made with the memory_save MCP tool. If your context feels thin after a compaction or reset, run mixai brief (or the context_brief MCP tool) to reload the latest objective, live workspace state, and the most relevant project memory without re-reading the repository. If you or the user hit a usage or rate limit, or the user asks to switch coding agents, call list_handoff_targets to see which other agents (Codex, Claude Code, Cursor, Antigravity) are installed and ready right now, then — only after the user confirms — call switch_to_provider to hand off: it checkpoints this session's work and launches the target agent with a continuation prompt.
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 · 11 lines · 268 tokens per session scan A adf322e0ceb8
mixai-memory is a cursor rule published in the GitHub repository thinhledev/mixai (2 stars, last pushed 2mo ago), licensed MIT. It adds 268 tokens to every session, about $0.0011 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
graphify
This project has a graphify knowledge graph at graphify-out/.
l00prite
This project uses the l00prite protocol: durable agent memory lives in .l00prite/, as plain files any AI agent can read, inside the protocol root — the l00prite/ folder at the repo root (memory at l00prite/.l00prite/; in the l00prite source repo the protocol root is the repo root itself). All .l00prite/ paths below…
avos-agent-workflow
Avos memory workflow for AI coding agents. Guides codebase search and history lookup.
memsprout
Cursor rule "memsprout" from memsprout/agents, covering using memsprout, search first, capturing, spaces and topics and files.
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.