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 rmarquesa/agentmemory-offline --skill session-historygit clone --depth 1 https://github.com/rmarquesa/agentmemory-offlineWrote 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/rmarquesa/agentmemory-offline/session-history)<a href="https://agentmods.dev/skills/rmarquesa/agentmemory-offline/session-history"><img src="https://agentmods.dev/badge/skills/rmarquesa/agentmemory-offline/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.1 | $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 6d 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.
This is a copy
100% identical to session-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 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.
- 6d ago First seen · 62 lines · 47 tokens per session scan A 6aec3cfd96a3
session-history is a skill published in the GitHub repository rmarquesa/agentmemory-offline (0 stars, last pushed 6d 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. It is 100% identical to session-history, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
day-log
Quick timestamped log entry — no conversation, just capture.
period-summary
Period summary (w/m/q/y) — reflect on the period, score it, close it out.
day-start
Day briefing — deliver context, capture what's happened, get moving.
erga-mcp
Use immediately when a user shares a job-posting URL—including a bare link or chat preview—and when organizing recruiting records, evaluating career evidence, or proposing a truthful résumé update through Erga MCP.
day-summary
Evening summary — reflect on the day, score it, close it out.
recap
Summarize the last N agent sessions for the current project, grouped by date, with highlight observations per session. Use when the user asks "recap", "what have we been doing", "today", "this week", or wants a rollup of recent work.