history-explorer

history-explorer is a skill for Claude Code, Codex from clawdotnet/openclaw.net. It costs 65 tokens per session (770 once invoked), scanned A, original, MIT.

A read-only tool for examining recent conversation turns and tool activity in an agent session.

In plain words
What is it for?
Use it to inspect turn counts, recent messages, tool usage, skill runs, and recurring tool or skill combinations.
Why use it?
It provides structured history when you need to understand what happened earlier, which tools were used, or how skills were combined.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: built for openclaw.

Good fit Use it to inspect turn counts, recent messages, tool usage, skill runs, and recurring tool or skill combinations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/clawdotnet/openclaw.net/history-explorer
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 clawdotnet/openclaw.net --skill history-explorer
Clone the repo
git clone --depth 1 https://github.com/clawdotnet/openclaw.net

Made for: Claude Code, Codex.

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 history-explorer

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/clawdotnet/openclaw.net/history-explorer"><img src="https://agentmods.dev/badge/skills/clawdotnet/openclaw.net/history-explorer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 770 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 pass 7 Sept 2026
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.00065 $0.00770
Opus 5.5 $0.00026 $0.00308
Sonnet 5.5 $0.00013 $0.00154
Haiku 4.5 $0.00006 $0.00077

Measured 1mo ago against content hash a00270c19df4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

history-explorer 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 1mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/explore.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.

src/OpenClaw.Gateway/skills/history-explorer/SKILL.md · 87 lines

How it starts

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

History Explorer

Read-only helper that inspects OpenClaw.NET session history for downstream workflows (especially meta-skill-creator).

What It Does

Parses a JSON session snapshot and returns structured analytics:

Key Description
turns Turn count, role distribution (user vs assistant), time span, recent turn previews
tools Tool invocation frequency, top tools, tool co-occurrence in the same turn
meta_runs Meta-skill execution history: skill name, status, step counts, failure codes
co_occurrences Skill/tool pairs that appear together across turns
placeholder Emitted when no session data is available; downstream workflows treat this as a signal to rely on user intent only

Input Contract

The script expects JSON session data on stdin. The calling agent should pipe a JSON object matching the Session schema — specifically:

{
  "id": "session-guid",
  "history": [
    { "role": "user", "content": "...", "timestamp": "..." },
    { "role": "assistant", "content": "...", "timestamp": "...", "toolCalls": [...] }
  ],
  "metaRunHistory": [
    {
      "runId": "...", "skillName": "...", "status": "completed",
      "startedAtUtc": "...", "completedAtUtc": "...",
      "stepResults": [
        { "id": "...", "kind": "...", "status": "...", "durationMs": 123 }
      ]
    }
  ]
}

Output Contract

Always returns a JSON object. When session data is available, includes the requested analytics keys. When unavailable or unparseable, returns a single placeholder key so downstream workflows degrade deterministically.

When to Use

  • Before running meta-skill-creator: feed co-occurrence and meta-usage data into the creator's proposal draft
  • When the user asks "what skills did I use recently" or "show my session history"
  • When debugging: inspect recent tool failures or meta-run error codes
  • When the agent needs to recall conversation context from earlier turns

Limitations

Read the full file on GitHub · 87 lines

Files

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.

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. 1mo ago First seen · 87 lines · 65 tokens per session scan A a00270c19df4

Subscribe to this mod's changes

history-explorer is a skill published in the GitHub repository clawdotnet/openclaw.net (527 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 770 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.

Related

Other skills, from other repositories

commonly

You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…

Team-Commonly/commonly · 0 tokens

github

Interact with GitHub (issues, PRs, repos, releases) using the gh CLI. Use when asked to read or write GitHub state — open an issue, fetch PR diff, comment, list runs, etc.

Team-Commonly/commonly · 49 tokens

pandic-office

Convert Markdown to PDF (or DOCX/EPUB/HTML) using the pandoc CLI. Use when asked to produce a PDF report, brief, summary, or any document where the input is Markdown and the output should be a polished, paginated file.

Team-Commonly/commonly · 59 tokens

pdf

Manipulate PDF files — extract text, count pages, render thumbnails, merge or split documents. Use for PDF-specific operations that don't fit markdown-converter (general read) or pandic-office (write from markdown).

Team-Commonly/commonly · 49 tokens

tmux

Manage long-running shell sessions with tmux — start a detached session, run a long task, reattach later, capture output. Use when a task takes longer than a single tool call (build, test, log tail).

Team-Commonly/commonly · 48 tokens

unity-development

Unity/C# development: MonoBehaviour lifecycle, ScriptableObjects, Addressables, URP/HDRP, physics, UI, editor scripting, and CLI builds.

CoWork-OS/CoWork-OS · 36 tokens