agentmemory is a persistent-memory system that lets AI coding agents retain and search information across sessions. It connects with several coding agents and MCP clients, storing knowledge with confidence scoring, lifecycle handling, knowledge graphs, and hybrid search. The catalogue contains agentmemory integrations such as skills, hooks, commands, a plugin, and an MCP component.
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 rohitg00/agentmemory --skill commit-historygit clone --depth 1 https://github.com/rohitg00/agentmemoryWrote 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/rohitg00/agentmemory/commit-history)<a href="https://agentmods.dev/skills/rohitg00/agentmemory/commit-history"><img src="https://agentmods.dev/badge/skills/rohitg00/agentmemory/commit-history/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/rohitg00/agentmemory/commit-history"><img src="https://agentmods.dev/badge/skills/rohitg00/agentmemory/commit-history.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00049 | $0.00552 |
| Opus 5.5 | $0.00020 | $0.00221 |
| Sonnet 5.5 | $0.00010 | $0.00110 |
| 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 3d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- commit-history — 100% identical, 2 lines differ
- commit-history — 100% identical, 2 lines differ
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 TROUBLESHOOTING.md if memory_commits is not available.
What ships with it
2 files 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.
- 3d ago Changed 233d70368cc8
- 1mo ago First seen · 63 lines · 49 tokens per session scan A 69f1379cfbc8
commit-history is a skill published in the GitHub repository rohitg00/agentmemory (29,595 stars, last pushed yesterday), licensed Apache-2.0. It adds 49 tokens to every session and 552 once invoked, about $0.0002 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
resolve-publish
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.
commit-messages
Write git commit messages and pull request titles in the WARP format used by the swarms repo.
feature-publish
Commit the feature, write the PR body, publish in the selected mode, and drive the PR.
devtu-github
GitHub workflow for ToolUniverse - push code safely by moving temp files, activating pre-commit hooks, running tests, and cleaning staged files. Use when pushing to GitHub, fixing CI failures, or cleaning up before commits.
release-notes
Draft a release note section from a commit range, grouped by what the reader gets.
install-skill
Install a community skill pack into this fork from a GitHub repo and ship it as an auto-merged PR.