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 TT-Wang/memem --skill memem-minegit clone --depth 1 https://github.com/TT-Wang/mememWrote 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/tt-wang/memem/memem-mine)<a href="https://agentmods.dev/skills/tt-wang/memem/memem-mine"><img src="https://agentmods.dev/badge/skills/tt-wang/memem/memem-mine/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/tt-wang/memem/memem-mine"><img src="https://agentmods.dev/badge/skills/tt-wang/memem/memem-mine.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 19 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Rogue Agent · line 9 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00026 | $0.00272 |
| Opus 5.5 | $0.00010 | $0.00109 |
| Sonnet 5.5 | $0.00005 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
memem-mine 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
Opt in to memem mining. In v2.1.0+ mining is event-triggered: it fires on every Claude Code Stop event when the opt-in marker exists. There is no daemon to start.
- Create the opt-in marker:
mkdir -p ~/.memem && touch ~/.memem/.miner-opted-in
- Tell the user:
- Mining is now active — every Stop event spawns a detached
mine_deltasubprocess that extracts memories from new turns since the last invocation - Hook overhead is ~50ms; the Haiku call runs in background
- Run
/memem-statusto check Stop-hook registration, opt-in marker, and last mine run - Safety net: SessionStart fires a stale-session sweep for any JSONLs > 10 min old not yet in
~/.memem/.mined_sessions(catches sessions where Stop never fired) - To opt out:
rm ~/.memem/.miner-opted-in(no daemon to stop — the hook just no-ops)
For backfilling pre-existing sessions, use /memem-mine-history.
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 · 22 lines · 26 tokens per session scan A fa88cb77ec90
memem-mine is a skill published in the GitHub repository TT-Wang/memem (32 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 272 once invoked, about $0.0001 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
skills
Your next session starts cold. No memory of what you built, what broke, what you decided. Every memory you write is a gift to that future session. The richer the memory, the less time re-learning.
stats
Show Captain Memo's corpus statistics (chunks per channel, observation counts, indexing progress, embedder info). Use when the user types /captain-memo:stats.
search
Hybrid search across Captain Memo's local memory + skills + observations. Use when the user types /captain-memo:search to retrieve top hits without the model having to decide whether to call searchall on its own.
doctor
Health probe across the worker, embedder, summarizer, queue, vector index, schema, cross-AI wiring and plugin install (cache and live versions). Use when the user types /captain-memo:doctor or when something seems wrong.
observations
List recent captured session observations (the summarized voyage logs). Use when the user wants to see what Captain Memo has logged from past sessions.
recall
Print the full content of a single Captain Memo hit by its docid. Used after /captain-memo:search to expand a snippet into the full source.