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/awizemann/scarf/memophantgit clone --depth 1 https://github.com/awizemann/scarfWrote 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/awizemann/scarf/memophant)<a href="https://agentmods.dev/rules/awizemann/scarf/memophant"><img src="https://agentmods.dev/badge/rules/awizemann/scarf/memophant.svg" alt="Measured on agentmods" 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 | $0.00588 | $0.00588 |
| Opus 5 | $0.00294 | $0.00294 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
memophant 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 today.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- memophant — 100% identical, 0 lines differ
What it actually says
Memory System (managed by Memophant) — core rules. Full reference: AGENTS.md.
- Memory is the source of truth. Search it before assuming; record durable decisions/learnings as memory notes or wiki pages — never in this file or session-private/model memory. Search before writing and edit an existing note (
edit_memory) rather than forking a near-duplicate. - Prefer the
memophantMCP tools for every read/write (search/read/write/edit/move) — read each tool's description (they document their args). The engine is the gate: the tool/app entry points carry the guards (slug-gen, structure validation, write-time secret scan); direct edits reconcile automatically but skip them — never compose your own guard set. Tools absent → grep the MAIN CHECKOUT's.memory/+wiki/; a git worktree's copy of those tiers is a base-commit snapshot and is stale by construction, so never grep./from one. - Don't
git add/committhe managed tiers (.memory/,wiki/,design/,code/,sessions/,documents/,vendors/,templates/,TASKS.md,tasks/) — the user commits each via Memophant's per-tier secret-scanned bar; leave them dirty. Everything else is yours. - Secrets → Keychain, never chat or files. Found or made a credential? Store it with
set_vendor_credential(fetch later withget_vendor_credential); never leave it loose in chat. - Agent artifacts (plans/reports/briefs) →
documents/(exact lowercase), viawrite_tier_file(tier: "documents", path: …)— never a repo'sdocs/folder (that's the project's own documentation) and never a case-variant likeDocuments/. - Read the project charter (
read_charter) at session start when this project has one (.memory/charter.md) — its commandments are absolute and OUTRANK memory notes, this file, and your brief; "No charter" is a normal answer. It's human-only: propose changes as a task taggedcharter, never edit it. File memory notes under one of six folders (architecture/conventions/decisions/operations/project/roadmap), never the root. When a note is grounded in code, passsource_paths(the repo files it depends on) so Memory Health can drift-check it — an unanchored code note can't be kept current.
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.
- today Changed · +1 lines · +110 tokens per session 53def41403bd
- 5d ago First seen · 16 lines · 478 tokens per session scan A 6195baa7fe13
memophant is a cursor rule published in the GitHub repository awizemann/scarf (841 stars, last pushed today), licensed MIT. It adds 588 tokens to every session, about $0.0029 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-30.
Other cursor rules, from other repositories
memophant
Memophant agent-instructions pointer.
knowledge-management-rule
Comprehensive knowledge management system for capturing, organizing, and applying project knowledge.
codegraph
CodeGraph MCP usage guide — when to use which tool.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.