Borrowing it
Nothing to install: this file belongs to kissrosecicd-hub/agents-evolution. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kissrosecicd-hub/agents-evolution/main/.agents/skills/session-recall/SKILL.mdgit clone --depth 1 https://github.com/kissrosecicd-hub/agents-evolutionWrote 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/kissrosecicd-hub/agents-evolution/session-recall)<a href="https://agentmods.dev/skills/kissrosecicd-hub/agents-evolution/session-recall"><img src="https://agentmods.dev/badge/skills/kissrosecicd-hub/agents-evolution/session-recall.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.00078 | $0.01141 |
| Opus 5 | $0.00039 | $0.00571 |
| Sonnet 5 | $0.00016 | $0.00228 |
| Haiku 4.5 | $0.00008 | $0.00114 |
Grade A, and why
session-recall 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Recall
Use local Codex logs instead of claimed model memory. Base the answer only on files found under CODEX_HOME_DIR="${CODEX_HOME:-$HOME/.codex}".
Primary Files
$CODEX_HOME_DIR/history.jsonl: fastest way to see recent user messages and map them tosession_id$CODEX_HOME_DIR/session_index.jsonl: thread names and timestamps$CODEX_HOME_DIR/sessions/YYYY/MM/DD/*.jsonl: full session transcripts$CODEX_HOME_DIR/archived_sessions/*.jsonl: fallback for older moved sessions
Treat config.toml, state_*.sqlite, and logs_*.sqlite as fallback only. Conversation recall should usually come from history.jsonl and sessions/.../*.jsonl.
Quick Workflow
- Identify the selector the user gave:
last,previous, specific date, date plus approximate time, keyword, project path, or session id. - Start from
history.jsonlto find candidatesession_idvalues and the user's own wording. - Open the matching
sessions/.../*.jsonlfile to reconstruct the conversation. - Answer with exact date and time when possible, name the session file used, and summarize only what the logs show.
- If multiple sessions match, say that and present the nearest 2-3 candidates instead of guessing.
Common Retrieval Patterns
Last or Previous Session
Use:
CODEX_HOME_DIR="${CODEX_HOME:-$HOME/.codex}"
tail -n 40 "$CODEX_HOME_DIR/history.jsonl"
ls -1t "$CODEX_HOME_DIR"/sessions/*/*/*/*.jsonl 2>/dev/null | head -10
If the user asks for the previous session while already in a new chat, do not return the current session. Pick the most recent distinct earlier session_id.
Specific Day
Use the exact calendar date, not relative wording:
CODEX_HOME_DIR="${CODEX_HOME:-$HOME/.codex}"
ls -1 "$CODEX_HOME_DIR/sessions/YYYY/MM/DD"/*.jsonl 2>/dev/null
rg -n 'YYYY-MM-DD|keyword|session_id' "$CODEX_HOME_DIR/history.jsonl"
If the user says "yesterday" or "that day", convert it to an absolute date in the answer.
Approximate Time on a Day
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.
- 8d ago First seen · 117 lines · 78 tokens per session scan A 43b6fdfd1379
session-recall is a skill published in the GitHub repository kissrosecicd-hub/agents-evolution (31 stars, last pushed 5mo ago), licensed MIT. It adds 78 tokens to every session and 1,141 once invoked, about $0.0004 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.