read-claude-code-history

read-claude-code-history is a skill for Claude Code from daymade/claude-code-skills. It costs 132 tokens per session (6,545 once invoked), scanned A, original, MIT.

A local history reader for Claude Code, Anthropic’s coding assistant. It finds past sessions, messages, events, and saved versions of deleted files without reopening the old work.

In plain words
What is it for?
Use it to list sessions, reconstruct a session timeline, search past conversations, recall earlier work, review how sessions ended, or recover deleted files.
Why use it?
It helps you recover facts from earlier coding sessions without accidentally continuing or changing that work.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

Part of the daymade-claude-code plugin — 21 skills shipped together

Good fit Use it to list sessions, reconstruct a session timeline, search past conversations, recall earlier work, review how sessions ended, or recover deleted files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/daymade/claude-code-skills/read-claude-code-history
About the project

Claude Code Skills Marketplace is a collection and marketplace of skills, plugins, agents, and instructions that extend Claude Code with specialized development workflows. It is for developers who want to install existing workflows or create, validate, and package their own Claude Code skills.

daymade/claude-code-skills · 1,516 stars · on GitHub

Install

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.

Any agent
npx skills add daymade/claude-code-skills --skill read-claude-code-history
Clone the repo
git clone --depth 1 https://github.com/daymade/claude-code-skills

Made for: Claude Code.

Or install daymade-claude-code, the plugin that ships this one along with the rest of its 21 skills.

Wrote 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.

agentmods badge for read-claude-code-history

README.md
[![agentmods](https://agentmods.dev/badge/skills/daymade/claude-code-skills/read-claude-code-history/github.svg)](https://agentmods.dev/skills/daymade/claude-code-skills/read-claude-code-history)
Your own site
<a href="https://agentmods.dev/skills/daymade/claude-code-skills/read-claude-code-history"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/read-claude-code-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.

agentmods 80×15 button for read-claude-code-history

Your own site · 80×15
<a href="https://agentmods.dev/skills/daymade/claude-code-skills/read-claude-code-history"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/read-claude-code-history.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 132 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,545 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 71
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00132 $0.06545
Opus 5.5 $0.00053 $0.02618
Sonnet 5.5 $0.00026 $0.01309
Haiku 4.5 $0.00013 $0.00654

Measured 8d ago against content hash 83ccb5ed17cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

read-claude-code-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 8d ago.

The scan reads SKILL.md. This mod also ships 35 executable files (scripts/_core/__init__.py, scripts/_core/claude.py, scripts/_core/codex.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

daymade-claude-code/read-claude-code-history/SKILL.md · 448 lines

How it starts

The opening of the file, as written. The whole thing — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Read Claude Code History

Read Claude Code evidence only. Do not resume the old process, edit its project, or turn a read request into a continuation task. When the user later asks to act, hand the verified evidence to daymade-claude-code:continue-claude-code-work.

Route by the requested result

User wants Use
Recent Claude Code sessions, titles, dates, or IDs Indexed metadata only; the bundled list_local_history.py currently reads all candidate bodies before date/limit filtering, so do not use it for a broad inventory
One known Session reconstructed as a chronological evidence briefing scripts/read_claude_session.py --session <ID>
Original tool input and paired result from one exact Session, selected by tool name, literal text, ordinal or time scripts/read_claude_session.py --session <ID> --tool-evidence --contains '<literal>'; see Original tool call/result evidence below
The exact command behind a hook audit row that records a Session ID and a command SHA-256 instead of the text scripts/read_claude_session.py --session <ID> --find-command-sha256 <HEX>; see Command behind a hook audit row below
Every Agent/Task tool_use in one Session, quoted verbatim (e.g. the exact prompt handed to an independent reviewer agent) scripts/read_claude_session.py --session <ID> --agent-prompts (optionally --agent-description-prefix TEXT); a prompt dispatched twice is listed twice
Which session launched a program in a known time window, across sessions scripts/analyze_sessions.py tool-calls --from <ISO> --to <ISO> --pattern <REGEX> [--tool NAME]; candidates are selected by filesystem metadata before any body is read, then grouped by session; Codex rollouts are out of scope and the gap is stated in the output
When hook runs happened across sessions — outcome, duration, exit code per run (e.g. "why was session startup slow", "did this guard fire today") scripts/analyze_sessions.py hook-events --from <ISO> --to <ISO> [--pattern <REGEX>] [--event NAME]; same candidate-first narrowing as tool-calls; forked-session copies of a run collapse to one; Codex rollouts are out of scope and the gap is stated in the output
The user's recent words, including human queued prompts scripts/extract_user_messages.py
A conversation or quote by keyword scripts/history_index.py recall --mode bm25, then the exact-session reader
Prior work whose wording may have changed scripts/history_index.py recall after checking index status
A topic with no known Session ID scripts/history_index.py status, then recall; state index coverage and freshness
The latest conversation about a topic, including a newer continuation Use recall to locate relevant project(s); for Codex, continue with read-codex-history's Latest topic across continuations route instead of treating relevance top-K as latest. Claude/Kimi have no indexed recent-session inventory here, so keep unverified continuation coverage unknown
How identified sessions or a physically bounded project ended Follow Inspect session endings in references/workflow_examples.md
A deleted/overwritten file preserved in Claude file-history records scripts/recover_content.py
How often each Skill ran and who started it (user command, model after the user named it, model unprompted), e.g. to decide model-visible vs user-invocable-only scripts/skill_usage_ledger.py index, then report (Claude and Codex together); see Skill usage ledger below
Kimi CLI sessions history_index.py recall --provider kimi, then read the named session's wire.jsonl; see Kimi CLI below
Continue a verified Claude session Stop reading and invoke daymade-claude-code:continue-claude-code-work

Read the full file on GitHub · 448 lines

Files

What ships with it

49 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.

Changes

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.

  1. 8d ago Changed · +6 lines 83ccb5ed17cd
  2. 12d ago Changed · +16 lines 09f54b5491aa
  3. 16d ago Changed · +6 lines 39ba43caf766
  4. 23d ago Changed · +59 lines bb4d32fd536e
  5. 1mo ago Changed · +3 lines · +38 tokens per session 42dd77c1c6f8
  6. 1mo ago Changed · +10 lines 956b0a2dc1b2
  7. 1mo ago Changed · +2 lines ab4a91712bf3
  8. 1mo ago Changed · +2 lines caa3d30de37b
  9. 1mo ago Changed · +21 lines 596f389e02c2
  10. 1mo ago First seen · 323 lines · 94 tokens per session scan A 10eb87d25a82

Subscribe to this mod's changes

read-claude-code-history is a skill published in the GitHub repository daymade/claude-code-skills (1,516 stars, last pushed yesterday), licensed MIT. It adds 132 tokens to every session and 6,545 once invoked, about $0.0005 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.

Related

read-claude-code-history compared with skills from other repositories

read-claude-code-history next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
read-claude-code-historydaymade/claude-code-skillsSkill1.5kyesterdayMITA132Claude Code
orbit-notionnexu-io/open-designSkill106kyesterdayApache-2.0A117Claude Code, Codex
agentmailpaperclipai/paperclipSkill111kyesterdayMITA30Claude Code, Codex
Cortexdanielmiessler/LifeOSSkill20kyesterdayMITA184Claude Code
rowboat-spacesrowboatlabs/rowboatSkill18kyesterdayApache-2.0A60Claude Code, Codex
feishuHmbown/CodeWhaleSkill41k5d agoMITA33Claude Code, Codex
pinchtab-mcppinchtab/pinchtabSkill11k10d agoMITA52Claude Code, Codex