What is mempenny-memory-triage?

A read-only command that reviews an automatic project-memory folder and proposes what to do with each item.

Use it to produce a table of suggested delete, archive, distill, or keep actions. It is an adapter for the OpenCode coding environment.

It lets you inspect cleanup decisions before changing anything, reducing the risk of deleting useful context or acting on unsafe instructions stored in memory files.

How marcelopaniza/mempenny configures Claude Code and OpenCode

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/marcelopaniza/mempenny/main/.opencode/commands/mempenny-memory-triage.md

Clone the repo

git clone --depth 1 https://github.com/marcelopaniza/mempenny

Made for: Claude Code, OpenCode.

Or install mempenny, the plugin that ships this one along with the rest of its 2 skills, 18 commands, 1 agent, 1 hook.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/marcelopaniza/mempenny/mempenny-memory-triage/github.svg)](https://agentmods.dev/commands/marcelopaniza/mempenny/mempenny-memory-triage)

Your own site

<a href="https://agentmods.dev/commands/marcelopaniza/mempenny/mempenny-memory-triage"><img src="https://agentmods.dev/badge/commands/marcelopaniza/mempenny/mempenny-memory-triage/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/marcelopaniza/mempenny/mempenny-memory-triage"><img src="https://agentmods.dev/badge/commands/marcelopaniza/mempenny/mempenny-memory-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 603 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00037	$0.00603
Opus 5	$0.00018	$0.00302
Sonnet 5	$0.00007	$0.00121
Haiku 4.5	$0.00004	$0.00060

Measured 12d ago against content hash 1e3cb472f7d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

mempenny-memory-triage 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 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.

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.

.opencode/commands/mempenny-memory-triage.md · 40 lines

How it starts

The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MemPenny memory-triage — opencode host adapter

The user invoked this command with: $ARGUMENTS

Execute the MemPenny memory-triage flow. The canonical procedure lives in:

${MEMPENNY_ROOT}/commands/memory-triage.md

Read it first with the Read tool — it is the single source of truth for the dry-run discipline, the 4-action vocabulary (DELETE / ARCHIVE / DISTILL / KEEP), the prompt-injection guard (H2), and the output table schema. This file only describes the opencode host differences.

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)

${MEMPENNY_CONFIG_PATH} if set.
Else ~/.claude/mempenny.config.json if ~/.claude/ exists.
Else ~/.config/opencode/mempenny.config.json.

C. Subagents (opencode Task tool)

The source spawns the triage as subagent_type: Explore. On opencode use subagent_type: "explore" (read-only), lowercase, passing description + prompt. Leave model unset unless MEMPENNY_TRIAGE_MODEL is exported.

D. Command namespace

Sibling commands use the hyphen namespace: /mempenny-clean, /mempenny-nap, /mempenny-restore, /mempenny-memory-apply, /mempenny-memory-distill, /mempenny-memory-curate, /mempenny-memory-shard-roll, /mempenny-memory-auto-split.

triage-specific notes

--dir, --only, --lang parse from $ARGUMENTS per the source Step 1.
The source's output contract is already strict — one markdown table + the totals block, nothing else, no prose before or after. Reproduce it exactly; do not invent a different schema or add a confidence column.
The per-invocation mktemp table path (H3) is what the user passes to /mempenny-memory-apply — surface it prominently, exactly as the source does.

Read the full file on GitHub · 40 lines

Changes

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 · 40 lines · 37 tokens per session scan A 1e3cb472f7d3

Subscribe to this mod's changes

mempenny-memory-triage is a command published in the GitHub repository marcelopaniza/mempenny (2 stars, last pushed 23d ago), licensed MIT. It adds 37 tokens to every session and 603 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-31.

Claude Code LLM Memory and context claude-plugin tokens triage

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…

yonatangross/orchestkit · 62 tokens

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…

yonatangross/orchestkit · 64 tokens

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).

yonatangross/orchestkit · 55 tokens

mempenny: Command for Claude Code