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.
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 daymade/claude-code-skills --skill read-claude-code-historygit clone --depth 1 https://github.com/daymade/claude-code-skillsWrote 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/daymade/claude-code-skills/read-claude-code-history)<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="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
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.
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.00163 | $0.01981 |
| Opus 5 | $0.00081 | $0.00991 |
| Sonnet 5 | $0.00033 | $0.00396 |
| Haiku 4.5 | $0.00016 | $0.00198 |
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 2d 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 — 179 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 | scripts/list_local_history.py --source claude |
| One known Session reconstructed as a chronological evidence briefing | scripts/read_claude_session.py --session <ID> |
| The user's recent words, including human queued prompts | scripts/extract_user_messages.py |
| A conversation, quote, file, tool result, or action by keyword | scripts/analyze_sessions.py search |
| Prior work whose wording may have changed | scripts/history_index.py recall after checking index status |
| How sessions in a time window ended | scripts/analyze_sessions.py triage |
| A deleted/overwritten file preserved in Claude file-history records | scripts/recover_content.py |
| Kimi CLI sessions — this Skill owns the only live Kimi surface | inventory: scripts/list_local_history.py --source kimi; full-text: scripts/analyze_sessions.py search --kimi |
| Continue a verified Claude session | Stop reading and invoke daymade-claude-code:continue-claude-code-work |
The requested output wins over the background story. If the user asks for a chronological table of their raw inputs, return that table; do not replace it with a topic analysis because their motivation mentions an incident.
Evidence surface and completeness
By default, discover every active Claude config home and every archive registered
in ~/.claude/history-sources.json. De-duplicate physical copies by Session ID and
content identity, and use record timestamps rather than file mtime. A result scoped
to one explicit --home is a diagnostic slice, not a completeness claim.
Treat Claude's record labels as storage metadata, not authorship proof. A top-level
type: user record can contain a command envelope, hook boilerplate, a whole pasted
document, agent-voiced text, or a system placeholder. Human text typed while the
assistant was busy can live in attachment.queued_command.prompt with
origin.kind: human; do not lose those corrections by reading only user records.
What ships with it
30 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.
- .INTEGRATION_SUMMARY.md 6.8 KB
- evals/evals.json 2.5 KB
- references/claude_session_format.md 7.9 KB
- references/hybrid_history_recall.md 9.9 KB
- references/legacy_cross_provider_workflow.md 29 KB
- references/session_file_format.md 26 KB
- references/workflow_examples.md 5.6 KB
- scripts/_core/__init__.py 1.3 KB runs code
- scripts/_core/claude.py 4.0 KB runs code
- scripts/_core/codex.py 16 KB runs code
- scripts/_core/homes.py 4.0 KB runs code
- scripts/_core/kimi.py 14 KB runs code
- scripts/_core/model.py 1.7 KB runs code
- scripts/_core/parse.py 6.2 KB runs code
- scripts/_core/sources.py 7.7 KB runs code
- scripts/_core/text.py 33 KB runs code
- scripts/analyze_sessions.py 124 KB runs code
- scripts/extract_user_messages.py 22 KB runs code
- scripts/history_index.py 69 KB runs code
- scripts/list_local_history.py 33 KB runs code
- scripts/read_claude_session.py 49 KB runs code
- scripts/recover_content.py 49 KB runs code
- tests/test_analyze_sessions.py 67 KB runs code
- tests/test_core_text.py 14 KB runs code
- tests/test_extract_user_messages.py 9.2 KB runs code
- tests/test_history_index.py 30 KB runs code
- tests/test_kimi_search.py 24 KB runs code
- tests/test_list_local_history.py 49 KB runs code
- tests/test_read_claude_session.py 20 KB runs code
- tests/test_recover_content.py 25 KB runs code
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.
- 2d ago Changed · +5 lines 8b64c594ad3f
- 4d ago Changed · +5 lines 025421e7ded4
- 8d ago First seen · 169 lines · 163 tokens per session scan A 8e1e455fb7c0
read-claude-code-history is a skill published in the GitHub repository daymade/claude-code-skills (1,381 stars, last pushed yesterday), licensed MIT. It adds 163 tokens to every session and 1,981 once invoked, about $0.0008 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
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…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.