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-codex-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-codex-history)<a href="https://agentmods.dev/skills/daymade/claude-code-skills/read-codex-history"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/read-codex-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.00127 | $0.01850 |
| Opus 5 | $0.00063 | $0.00925 |
| Sonnet 5 | $0.00025 | $0.00370 |
| Haiku 4.5 | $0.00013 | $0.00185 |
Grade A, and why
read-codex-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 7d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read Codex History
Read Codex evidence only. Do not continue the old task or change its project. If
the user wants execution after the read is complete, pass the verified evidence
to daymade-claude-code:continue-codex-work.
Codex has three different history surfaces
| Surface | Authority | Use |
|---|---|---|
<codex-home>/history.jsonl |
What the user submitted, keyed by Session ID and internal epoch timestamp | Exact recent user-input tables |
state_*.sqlite |
Inventory metadata such as cwd, title, update time, and rollout path | Fast listing and candidate discovery |
sessions/**/rollout-*.jsonl and archived_sessions/** |
Full user/assistant/tool/compaction/fork event stream | Session evidence, lineage, behavior audit, and keyword search |
Do not substitute one surface for another. A prompt-ledger row proves what was
submitted, not what the Agent answered. A state DB path is only a candidate until
the rollout's session_meta.id matches. A rollout can exist without a prompt-ledger
row, and a /fork prompt can exist without a child rollout.
Read references/storage_and_portability.md for source discovery, timestamps, writer-lock semantics, legacy Kimi compatibility, and storage failures. Read references/codex_rollout_format.md before interpreting fork snapshots, compaction, event streams, or end reasons.
Route by the requested result
| User wants | Use |
|---|---|
| Recent Codex sessions, titles, IDs, or positive writer-lock evidence | scripts/list_local_history.py --source codex |
| Exact recent user inputs from newest to oldest, grouped by Session | scripts/list_codex_user_inputs.py |
| Locate one exact rollout by internal identity | scripts/analyze_sessions.py locate-codex <ID> |
| Reconstruct one Session and its declared parent snapshots | scripts/read_codex_session.py --session <ID> |
| Search full rollout events by keyword | scripts/analyze_sessions.py search --codex-only |
| Continue after evidence is complete | Stop reading and invoke daymade-claude-code:continue-codex-work |
What ships with it
23 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.
- .security-scan-passed 187 B
- evals/evals.json 2.4 KB
- references/codex_rollout_format.md 11 KB
- references/legacy_multi_provider_inventory.md 14 KB
- references/storage_and_portability.md 17 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 115 KB runs code
- scripts/list_codex_user_inputs.py 11 KB runs code
- scripts/list_local_history.py 33 KB runs code
- scripts/read_codex_session.py 62 KB runs code
- tests/test_analyze_sessions.py 55 KB runs code
- tests/test_kimi_provider.py 18 KB runs code
- tests/test_list_codex_user_inputs.py 7.2 KB runs code
- tests/test_list_local_history.py 52 KB runs code
- tests/test_read_codex_session.py 54 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.
- 7d ago First seen · 169 lines · 127 tokens per session scan A 2ea7ee7eff27
read-codex-history is a skill published in the GitHub repository daymade/claude-code-skills (1,377 stars, last pushed yesterday), licensed MIT. It adds 127 tokens to every session and 1,850 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…