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 skills/rodolfochicone/rc-project/rc-memorynpx skills add rodolfochicone/rc-project --skill rc-memorygit clone --depth 1 https://github.com/rodolfochicone/rc-projectWrote 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/skills/rodolfochicone/rc-project/rc-memory)<a href="https://agentmods.dev/skills/rodolfochicone/rc-project/rc-memory"><img src="https://agentmods.dev/badge/skills/rodolfochicone/rc-project/rc-memory.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.00034 | $0.01727 |
| Opus 5 | $0.00017 | $0.00864 |
| Sonnet 5 | $0.00007 | $0.00345 |
| Haiku 4.5 | $0.00003 | $0.00173 |
Grade A, and why
rc-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory
The one place for what RC remembers about this project across turns and sessions. Project-scoped only — never copy memory to another project or a global location. Plain markdown plus one machine-owned JSON store; this skill never edits source code.
.rc/memory/
INDEX.md # one line per fact — the recall entry point
<slug>.md # one durable fact per file
lessons.json # machine-owned lesson store (scripts/lessons.mjs) — do NOT hand-edit
LESSONS.md # rendered playbook, regenerated on every write
observations.jsonl # raw capture appended by the observe hook (transient)
Resolve the project's .rc base directory (nearest .rc walking up; default ./.rc).
Routing
The shape of the knowledge decides where it goes; first match wins.
| The knowledge is… | Goes to |
|---|---|
| a standalone statement — a decision, convention, gotcha, term | A — Facts |
| something a verification signal or a user correction taught us | B — Lessons |
| a multi-step route with commands, a required order, and dead-ends | C — Golden paths |
| only true while one task runs | Scratch, below |
| a one-off unlikely to recur | nowhere — drop it |
A — Facts
One <slug>.md per fact, frontmatter plus a short body:
---
title: <short title>
scope: decision | convention | gotcha | glossary | context
tags: [a, b]
created: <YYYY-MM-DD>
updated: <YYYY-MM-DD>
---
<the fact in a few sentences. For a decision, add **Why:** and, if useful, **How to apply:**.>
INDEX.md holds one line per fact, newest last: - [<title>](<slug>.md) — <scope> — <one-line hook>.
It is the only file you read to decide relevance; never dump fact bodies into it.
Consult before implementing, deciding or planning: read INDEX.md, scan the hooks for the task's
terms, open only the matching <slug>.md. For a large store, grep -ri "<term>" .rc/memory/.
Record only when all three hold: (1) a future run needs it to avoid a mistake or rediscovery; (2) it is durable for this project, not one task's execution; (3) it is not already obvious from the repo, git history, or the spec. Reuse the slug to update rather than duplicate. Never store secrets, tokens, credentials, large code blocks, stack traces or raw session logs.
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.
- 5d ago First seen · 140 lines · 34 tokens per session scan A 4899e5089274
rc-memory is a skill published in the GitHub repository rodolfochicone/rc-project (19 stars, last pushed 29d ago), licensed MIT. It adds 34 tokens to every session and 1,727 once invoked, about $0.0002 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 skills, from other repositories
mem0-tour
Browses all stored memories grouped by category with full content display. Use when reviewing all project memories, exploring stored knowledge, onboarding to a project, or getting an overview of captured decisions, conventions, and learnings.
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…
stats
Displays memory usage statistics for the current session and project including counts by category, age distribution, and API latency. Use when checking how many memories exist, reviewing session activity, or auditing memory distribution across categories.
peek
Searches memories and displays compact one-liner results, or looks up a specific memory by ID. Use for quick memory lookups, checking if a decision was recorded, resolving [mem0:id] citations, or browsing memories without full category detail.
pause
Pause Mem0 memory capture on this machine. Use when the user wants to stop memories being recorded, for example for private work or experiments.
mine
Mine a project or conversation into your MemPalace — extract and store memories for later retrieval.