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/rohitg00/agentmemory/session-historynpx skills add rohitg00/agentmemory --skill session-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/session-history)<a href="https://agentmods.dev/skills/rohitg00/agentmemory/session-history"><img src="https://agentmods.dev/badge/skills/rohitg00/agentmemory/session-history.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.00452 |
| Opus 5 | $0.00023 | $0.00226 |
| Sonnet 5 | $0.00009 | $0.00090 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
session-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 4d 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:
- session-history — 100% identical, 0 lines differ
- session-history — 91% identical, 5 lines differ
What it actually says
The user wants an overview of recent sessions on this project.
Quick start
memory_sessions { "limit": 20 }
Expected output:
7f3a9c2 · app · 2026-06-07 09:00 · completed · 14 obs
- decision: Rotate refresh tokens on every use
b21d004 · app · 2026-06-05 14:00 · completed · 9 obs
- code: limit.ts counts per-IP
Why
Only show sessions and observations the tool returned. An empty history is a real answer, never a cue to invent past work.
Workflow
- Call
memory_sessionswithlimit: 20for a meaningful window. - Present in reverse chronological order: session id (first 8), project, start time, status.
- For sessions with observations, show the key highlights (type plus title).
- Note the total observation count per session.
- When a session summary exists, surface its title and the key decisions.
Anti-patterns
WRONG: the tool returns two sessions, you describe "several sessions of steady progress" and add ones you remember from the conversation.
RIGHT: show exactly the two sessions returned, each with its real id, status, and observation count.
Checklist
- Every session shown came from the tool response.
- Order is reverse-chronological.
- Per-session observation counts match the response.
- No session or highlight was invented or merged.
See also
recap: same data grouped by date with highlights.handoff: jump straight into the most recent session.recall: search across all sessions by topic.
Troubleshooting
See ../_shared/TROUBLESHOOTING.md if memory_sessions 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.
- 4d ago First seen · 62 lines · 47 tokens per session scan A 6aec3cfd96a3
session-history is a skill published in the GitHub repository rohitg00/agentmemory (27,975 stars, last pushed 3d ago), licensed Apache-2.0. It adds 47 tokens to every session and 452 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-30.
Other skills, from other repositories
trellis-session-insight
Reach into past AI conversation history through the trellis mem CLI. Use whenever the user asks 'how did we solve X last time', 'have we discussed this before', 'what was the decision on X', 'remind me what we did in this task', '上次怎么解的', '之前讨论过吗', '想起一段对话', or when starting a brainstorm that overlaps prior work…
agentcairn-setup
Install, configure, verify, upgrade, or repair AgentCairn persistent cross-agent memory. Use when a user wants shared local-first memory in Claude Code, Codex, Cursor, OpenCode, Antigravity, VS Code, Claude Desktop, or another supported harness; when AgentCairn recall or remember tools are missing; or when its plugin…
Incident Response & Digital Forensics
IR playbook execution, evidence collection, forensic timeline analysis, memory forensics, and post-incident reporting following NIST SP 800-61 and SANS PICERL methodology.
rgit-digest
Use when a research-git digest queue has pending units (rgit digest status) — after rgit init staged a history-digestion plan, or when the user asks to backfill, digest, or import git history into capsules. Batches run on the host session's subscription and progress is resumable, so partial sessions are fine.
rgit-recall
Use when the user wants to recall, resurrect, bring back, or re-apply a previously captured feature/idea onto today's codebase (e.g. "bring back the re-ranking retrieval step").
using-agentcairn-memory
Use when AgentCairn memory tools are loaded and starting a non-trivial task or finishing a decision/fix — recall prior memory before working, and remember durable facts worth carrying across sessions.