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 local-conversation-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/local-conversation-history)<a href="https://agentmods.dev/skills/daymade/claude-code-skills/local-conversation-history"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/local-conversation-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.
<a href="https://agentmods.dev/skills/daymade/claude-code-skills/local-conversation-history"><img src="https://agentmods.dev/badge/skills/daymade/claude-code-skills/local-conversation-history.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00084 | $0.02592 |
| Opus 5.5 | $0.00034 | $0.01037 |
| Sonnet 5.5 | $0.00017 | $0.00518 |
| Haiku 4.5 | $0.00008 | $0.00259 |
Grade A, and why
local-conversation-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.
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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Conversation History — router
This skill decides which skill runs. It does not parse history itself, does not own commands for a single provider, and never re-implements what an executor already does. If you find yourself explaining flags for one provider, you are in the wrong skill — hand off and stop.
Route by platform × action
For a backup-health request ("are our conversation backups working?" / "历史备份是否正常"),
read the owning backup configuration and storage SOP before selecting a history reader.
Use git-large-files-storage-setup's backup-health workflow when that Skill is installed;
otherwise use the existing storage owner's procedure and report any missing dependency.
Keep this route read-only. Verify provider/source coverage, the actual backup round,
destination originals, recovery samples and the alert job separately. Do not resume a
paused collector or rebuild an index to check a backup. Use provider readers only for
selected original/session identity checks, not conversation-body searches to discover
backup jobs. Keep account, machine and credential paths in the user's owning configuration.
Establish two things before routing: which platform the conversation lived on, and whether the user wants evidence (what was said/done) or resumption (take the work forward).
| Platform | Read evidence | Continue the work |
|---|---|---|
| Claude Code | daymade-claude-code:read-claude-code-history |
daymade-claude-code:continue-claude-code-work |
| OpenAI Codex | daymade-claude-code:read-codex-history |
daymade-claude-code:continue-codex-work |
| Kimi CLI | read-claude-code-history, with the Kimi scope named — see Provider scope |
no continuation skill exists |
Resumption always follows a read. The continuation skills require a verified read receipt; routing straight to them without one is a defect, not a shortcut.
When the platform is not stated, separate an exact identity from a memory of content. With a complete session ID, first use the Codex exact-ID locator, then the Claude Code exact-session lookup if Codex does not verify it. The verified original record decides the provider and continuation skill; an ID prefix does not. With only a title, date, quote, or remembered topic, use the inventory or content-search route below and verify the original messages before assigning a provider.
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.
- 8d ago Changed · +1 lines 3431d0aea8e1
- 28d ago Changed · +11 lines 3162db7fe30c
- 1mo ago Changed · +30 lines 75fb60a1f2c8
- 1mo ago Changed · -8 lines 19ca34133dc8
- 1mo ago Changed · -27 lines · -130 tokens per session 02cac7185d52
- 1mo ago Changed · +17 lines a9c03a7e5b33
- 1mo ago Changed · +9 lines 8c6d6958c6e7
- 1mo ago Changed · +28 lines 535bd2b3b976
- 2mo ago First seen · 117 lines · 214 tokens per session scan A 0801ba4677ce
local-conversation-history is a skill published in the GitHub repository daymade/claude-code-skills (1,516 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 2,592 once invoked, about $0.0003 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.
local-conversation-history compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| local-conversation-historydaymade/claude-code-skills | Skill | 1.5k | yesterday | MIT | A | 84 | Claude Code |
| knowledge-ingestopenclaw/openclaw | Skill | 394k | yesterday | MIT | A | 80 | Claude Code, Codex |
| mem0-oss-to-platformmem0ai/mem0 | Skill | 68k | 2d ago | Apache-2.0 | A | 217 | Claude Code, Codex |
| forgetasgeirtj/system_prompts_leaks | Skill | 71k | 2d ago | CC0-1.0 | A | 74 | Claude Code, Codex |
| Cortexdanielmiessler/LifeOS | Skill | 20k | yesterday | MIT | A | 184 | Claude Code |
| memoryopensquilla/opensquilla | Skill | 7.1k | 6d ago | Apache-2.0 | A | 44 | Claude Code, Codex |
| ha-data-storesshiwenwen/hope-agent | Skill | 1.9k | yesterday | MIT | A | 115 | Claude Code, Codex |