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 mblode/agent-skills --skill chat-historygit clone --depth 1 https://github.com/mblode/agent-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/mblode/agent-skills/chat-history)<a href="https://agentmods.dev/skills/mblode/agent-skills/chat-history"><img src="https://agentmods.dev/badge/skills/mblode/agent-skills/chat-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/mblode/agent-skills/chat-history"><img src="https://agentmods.dev/badge/skills/mblode/agent-skills/chat-history.svg" alt="Reviewed on agentmods" width="80" 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.01282 |
| Opus 5 | $0.00039 | $0.00641 |
| Sonnet 5 | $0.00016 | $0.00256 |
| Haiku 4.5 | $0.00008 | $0.00128 |
Grade A, and why
chat-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 today.
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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chat History
- IS: recover historical context with source evidence: prior fixes, decision trails, exact passages and what followed, research across sessions.
- IS NOT: browsing history, automatic memory writing, or proof of current repository or production state. For Obsidian notes use
obsidian; for recent computer activity use an available computer-history capability.
Agent compatibility
The same skill and bundled script run in Codex, Grok, Cursor, and Claude Code. The model does not select the source adapter: every host can search every accessible supported source. No vendor SDK, host-specific tool names, or Claude-only substitutions are required. Read host setup when installing, moving between hosts, or diagnosing unavailable tools.
Workflow
- Discover available evidence. Resolve
scripts/history.pyrelative to this installed SKILL.md, then execute it withpython3. Rundiscoverto report local source paths. Use explicit exports for web conversations; local Codex sessions do not include ChatGPT web history. Missing access is a coverage gap, not an empty search result. - Search narrowly, widen deliberately. Choose distinctive terms from the user's defect, artifact, project, or quoted passage. Start with known project/session paths; for cross-project research search the selected source roots. Batch spelling variants with repeated
-eflags. Search results are literal OR matches in encounter order, not exhaustive or relevance-ranked when capped. Search both user and assistant messages; use--role userto locate the original request. Read source adapters when choosing paths, using Cursor/exports, or handling unsupported formats. - Read the sequence. Use each hit's path and line/key to read surrounding turns. Follow later corrections, linked sessions, commits, plans, and artifacts when they affect the answer. For "what followed", include assistant and tool evidence after the exact occurrence. A final summary alone may conceal scope changes. Expand a truncated window or repeat the search with a more specific term when evidence is incomplete.
- Answer with provenance. Lead with the recovered finding, cite the source path plus line or session/message key, and explain any later correction. Distinguish user intent, proposed work, reported completion, tool evidence, and current verification. Report material coverage gaps and conflicting evidence. Verify today's state separately when the task depends on it.
What ships with it
7 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.
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.
- today First seen · 54 lines · 78 tokens per session scan A 204730b0da73
chat-history is a skill published in the GitHub repository mblode/agent-skills (108 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 1,282 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-09-10.
Other skills, from other repositories
memory
Unified project memory management: update, prune, reflect, and maintain knowledge. Combines conversation scanning, deduplication, contradiction detection, confidence scoring, and consistency checks in a single skill. Usage: /memory update [topic] — scan conversation, persist learnings /memory prune [type] — find…
honcho
Configure and troubleshoot Honcho memory for Hermes.
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
hermes-agent
Use, configure, theme, extend, and orchestrate Hermes Agent.
taiyi-compress
A workflow tool for shrinking large coding-agent conversations and work files into shorter context notes. It can also coordinate separate agents for parallel development and create handoff notes for continuing work in a new session.
token-optimization
Use when the user says 'token optimization', 'save tokens', 'context window', 'reduce tokens', 'token stack', or 'TokenStack', or asks about extending context window capacity. Covers TokenStack, the built-in compression proxy that shrinks Claude Code tool output before it reaches the Anthropic API. Do NOT use for…