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 agentmods add skills/rmarquesa/agentmemory-offline/commit-historynpx skills add rmarquesa/agentmemory-offline --skill commit-historygit clone --depth 1 https://github.com/rmarquesa/agentmemory-offlineWhat 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 | $0.00049 | $0.00545 |
| Opus 5 | $0.00024 | $0.00272 |
| Sonnet 5 | $0.00010 | $0.00109 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
commit-history 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 yesterday.
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.
This is a copy
100% identical to commit-history — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
The user wants a list of agent-linked commits. Filter args: $ARGUMENTS
Quick start
memory_commits { "branch": "main", "limit": 20 }
Expected output:
9a1b2c3 main 2026-06-07 "rotate refresh tokens" · session 7f3a9c2 (14 obs)
b21d004 main 2026-06-05 "rate limiter audit" · session b21d004 (9 obs)
Why
Render only the commits the tool returned, newest first. An empty result means the filter matched nothing, not that work is missing.
Workflow
- Parse
$ARGUMENTSforbranch=<name>,repo=<url-or-fragment>,limit=<n>. A bare numeric token is the limit. Defaults: no branch, no repo, limit 100, max 500. - Call
memory_commitswith the parsed filters. - Render reverse-chronologically: short sha, branch, authored timestamp, first
line of the message, linked session id(s) (first 8) with observation counts,
and file count when
filesis present. - Empty result: tell the user the filter matched nothing and suggest dropping the branch or repo filter.
Anti-patterns
WRONG (REST fallback): concatenate ?branch= + raw branch name, so a name with
?, &, or # corrupts the query string.
RIGHT: URL-encode every value with URLSearchParams/encodeURIComponent before
appending to GET /agentmemory/commits.
Checklist
- Filters parsed; bare number treated as limit; limit capped at 500.
- Output is reverse-chronological.
- Session ids and observation counts come straight from the response.
- REST fallback URL-encodes branch, repo, and limit.
See also
commit-context: drill into one commit's session.recall: search the observations behind a linked session.
Troubleshooting
See ../_shared/TROUBLESHOOTING.md if memory_commits is not available.
What ships with it
1 file 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.
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.
- yesterday First seen · 63 lines · 49 tokens per session scan A 69f1379cfbc8
commit-history is a skill published in the GitHub repository rmarquesa/agentmemory-offline (0 stars, last pushed 2d ago), licensed Apache-2.0. It adds 49 tokens to every session and 545 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to commit-history, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
plur-memory
Persistent learning for AI agents. Open engram format. Your agent learns from corrections, remembers across sessions, and transfers knowledge across domains.
plur-session-end
Extract durable learnings at the end of a session. Saves corrections, preferences, and codebase patterns as engrams — nothing ephemeral, nothing sensitive.
plur-memory
Your memory stays on your machine. No cloud, no tracking, no API key. PLUR makes your OpenClaw remember — and shares that memory with every other tool you use.
compartmentalize
Sweep this conversation and save everything potentially worth knowing again into Compartment, the encrypted memory vault. Run it before compacting or summarizing so nothing is lost to the summary, or on its own at any point to bank the session.
paxm
Recall or remember durable project context with paxm.
reduce
Use when asked to simplify, clean up, tidy, or refactor code for clarity without changing what it does, or when the user says "simplify this", "clean this up", "make it readable", "reduce the complexity", or "tidy this". Behavior-preserving only; not a bug or security audit (use bug-hunt or security-sweep for those).