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.
git clone --depth 1 https://github.com/josephy02/gitmemWrote 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/josephy02/gitmem/remember)<a href="https://agentmods.dev/commands/josephy02/gitmem/remember"><img src="https://agentmods.dev/badge/commands/josephy02/gitmem/remember/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/josephy02/gitmem/remember"><img src="https://agentmods.dev/badge/commands/josephy02/gitmem/remember.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.00010 | $0.00198 |
| Opus 5.5 | $0.00004 | $0.00079 |
| Sonnet 5.5 | $0.00002 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
remember 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
Save the following to persistent memory using the gitmem memory_append MCP tool: $ARGUMENTS
Rules:
- One self-contained claim per event. If the input contains several distinct facts, append them separately.
- Use
kind: "decision"when it records a choice ("we use X", "do not refactor Y");kind: "observation"otherwise. - Pick a scope from the existing scope hierarchy (check
memory_factsif unsure); default to the project's top-level scope. - If it contradicts or updates an existing memory, append it as a
correctionwithsupersedesset to the old event id instead of a plain observation. - If no argument was given, review this conversation and save the durable facts and decisions worth keeping — skip anything the repo or git history already records.
Confirm what was saved with the returned event id(s).
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 · 15 lines · 10 tokens per session scan A e77e211f8175
remember is a command published in the GitHub repository josephy02/gitmem (0 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 198 once invoked, about $0.0000 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-31.
Other commands, from other repositories
unforgit
Show Unforgit repository-memory status and suggest the next useful action.
unforgit-health
Inspect Unforgit memory health.
unforgit-recall
Search Unforgit memory for context relevant to the user's current request.
unforgit-curate
Review and improve Unforgit memory quality.
dream-apply
Walk a dream proposal artifact, review each item, apply accepted ones, commit.
end
End a session — log what happened and propose durable memory updates.