Borrowing it
Nothing to install: this file belongs to marcelopaniza/mempenny. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/marcelopaniza/mempenny/main/.opencode/commands/mempenny-nap.mdgit clone --depth 1 https://github.com/marcelopaniza/mempennyWrote 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/commands/marcelopaniza/mempenny/mempenny-nap)<a href="https://agentmods.dev/commands/marcelopaniza/mempenny/mempenny-nap"><img src="https://agentmods.dev/badge/commands/marcelopaniza/mempenny/mempenny-nap/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/commands/marcelopaniza/mempenny/mempenny-nap"><img src="https://agentmods.dev/badge/commands/marcelopaniza/mempenny/mempenny-nap.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.00042 | $0.00753 |
| Opus 5 | $0.00021 | $0.00377 |
| Sonnet 5 | $0.00008 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade C, and why
mempenny-nap scanned grade C with 2 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 12d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
**Read it first with the Read tool** — it is the single source of truth for the schedule schema, the config upsert discipline, the symlink guard, and `chmod 600`. This file only describes the opencode host differences. Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Skip the `~/.claude/settings.json` → `autoMemoryEnabled` subroutine entirely; opencode has no equivalent. How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MemPenny nap — opencode host adapter
The user invoked this command with: $ARGUMENTS
Execute the MemPenny nap (schedule) flow. The canonical procedure lives in:
${MEMPENNY_ROOT}/commands/nap.md
Read it first with the Read tool — it is the single source of truth for the schedule schema, the config upsert discipline, the symlink guard, and chmod 600. This file only describes the opencode host differences.
While executing the source procedure, apply these opencode host adaptations (override the source wherever they conflict):
A. Paths & environment
The env shim sets MEMPENNY_HOST=opencode, MEMPENNY_ROOT, MEMPENNY_DATA_DIR. Substitute:
${CLAUDE_PLUGIN_ROOT}→${MEMPENNY_ROOT}${CLAUDE_PLUGIN_DATA}→${MEMPENNY_DATA_DIR}${CLAUDE_PROJECT_DIR}→ the current working directory
B. Config path (shared with Claude Code)
Same host-aware rule as the other commands:
${MEMPENNY_CONFIG_PATH}if set.- Else
~/.claude/mempenny.config.jsonif~/.claude/exists. - Else
~/.config/opencode/mempenny.config.json.
Apply F-M2 + L1 exactly as the source specifies.
C. Auto-memory (Claude Code-only)
Skip the ~/.claude/settings.json → autoMemoryEnabled subroutine entirely; opencode has no equivalent.
D. Where the schedule fires
The source (nap.md) says the cleanup fires via a plugin-shipped SessionStart hook the next time you open Claude Code. On opencode the equivalent is the TS plugin at .opencode/plugins/mempenny-nap.ts, which listens for opencode's session.created event (root sessions only) through the plugin API's generic event hook.
Notify is the default: when a nap comes due, the plugin shows a desktop notification telling you to run /mempenny-clean --yes; nothing runs without you. "mode": "auto" is an explicit opt-in: with it set on the schedule entry, the plugin starts /mempenny-clean --yes in the new session itself (SDK session.command); a failed invoke falls back to the notification.
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.
- 12d ago First seen · 49 lines · 42 tokens per session scan C 7dd7a53eeec3
mempenny-nap is a command published in the GitHub repository marcelopaniza/mempenny (2 stars, last pushed 23d ago), licensed MIT. It adds 42 tokens to every session and 753 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (asks for root, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
remember
Stores decisions, patterns, and outcomes in the MCP memory knowledge graph as entities with typed observations and relations. Supports recording architectural decisions, anti-patterns, tool preferences, workflow outcomes, and project conventions that persist across sessions. Use when saving patterns, remembering…
memory
Unified read-side memory operations including knowledge graph search, session context loading, decision timeline viewing, and Mermaid graph visualization. Subcommands: search, load, history, viz, status. Complements /ork:remember (write-side). Use when searching past decisions, loading context, or visualizing the…
recall-loop
Periodic memory digest — designed for use with Claude Code's /loop scheduler. Shows recent memories and pending to-dos in a compact, scannable format.
pull-learnings
Pulls shared organization patterns into local org-patterns.toon.
dream
Nightly memory consolidation — prunes stale entries, merges duplicates, resolves contradictions, rebuilds MEMORY.md index. Use when memory files have accumulated over many sessions and need cleanup. Do NOT use for storing new decisions (use remember) or searching memory (use memory).
fire-session-summary
Auto-generate compact session summary with aggregate status, readiness, outlook, and next steps.