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 skills add NevaMind-AI/memU --skill memugit clone --depth 1 https://github.com/NevaMind-AI/memUWrote 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/nevamind-ai/memu/memu)<a href="https://agentmods.dev/skills/nevamind-ai/memu/memu"><img src="https://agentmods.dev/badge/skills/nevamind-ai/memu/memu/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/skills/nevamind-ai/memu/memu"><img src="https://agentmods.dev/badge/skills/nevamind-ai/memu/memu.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.00061 | $0.01846 |
| Opus 5.5 | $0.00024 | $0.00738 |
| Sonnet 5.5 | $0.00012 | $0.00369 |
| Haiku 4.5 | $0.00006 | $0.00185 |
Grade A, and why
install-memu 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
25 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/banner.png 258 KB
- assets/benchmark.png 77 KB
- assets/memorize.png 889 KB
- assets/memUbot.png 285 KB
- assets/partners/buddie.png 13 KB
- assets/partners/bytebase.png 23 KB
- assets/partners/Clawdchat.png 470 KB
- assets/partners/jazz.png 31 KB
- assets/partners/LazyLLM.png 248 KB
- assets/partners/openagents.png 15 KB
- assets/partners/xroute.png 44 KB
- assets/qrcode.png 161 KB
- assets/retrieve.png 840 KB
- assets/skill-extraction.png 1326 KB
- assets/star.gif 3004 KB
- assets/structure-v2.png 1349 KB
- assets/structure.png 1633 KB
- assets/usecase/ai_companion-0000.jpg 19 KB
- assets/usecase/ai_creation-0000.jpg 19 KB
- assets/usecase/ai_edu-0000.jpg 22 KB
- assets/usecase/ai_ip-0000.png 556 KB
- assets/usecase/ai_robot-0000.jpg 14 KB
- assets/usecase/ai_role_play-0000.jpg 25 KB
- assets/usecase/ai_therapy-0000.jpg 16 KB
- scripts/db.py 3.1 KB runs code
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 Changed · +1 lines 9d576f9d50b8
- 1mo ago First seen · 170 lines · 61 tokens per session scan A f954b1b8a452
install-memu is a skill published in the GitHub repository NevaMind-AI/memU (14,546 stars, last pushed 3d ago), with no licence file. It adds 61 tokens to every session and 1,846 once invoked, about $0.0002 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-30.
Other skills, from other repositories
agent-memory-discipline
Rules for when an agent should recall from long-term memory before acting and when it should save decisions, corrections and failures afterwards. Works with any memory backend.
openviking-context-database
Use OpenViking from OpenClaw through @openviking/openclaw-plugin: long-term memory, session archives, resource and Agent Skill import, semantic recall, recall trace debugging, and externalized tool-result recovery. Prefer this skill when the user wants to use, query, debug, or operate OpenViking context from an…
context-engineering-review
Review what an LLM feature or agent actually puts in its context window — and find what's bloating, missing, or fighting itself. Use when asked to review a system prompt and context assembly, cut token usage without losing quality, debug an agent that ignores instructions, or audit how retrieval results, history, and…
self-improve
Extract lessons from the current session, or sweep the project's past sessions when asked, and route them to the appropriate knowledge layer (project AGENTS.md, auto memory, existing skills, or new skills). Use when the user asks to "self-improve", "distill this session", "distill past sessions", "sweep past…
memory-file-maintenance
Keep your AI memory/context file (MEMORY.md, CLAUDE.md, custom instructions) healthy over time — pruning the stale, adding the new, and keeping it sharp so your AI keeps getting you right. Use when asked review my memory file, my AI context is outdated, clean up my CLAUDE.md, or maintain my AI instructions. Produces a…
recall-rationale
Recall why a past change was made by locating the Claude Code transcript that produced it. Use when the user asks to "recall the rationale", "find the rationale", "look up the rationale", "why did I do X", "why did we do X", "why was this changed", or "find the transcript for this commit".