Inspect CCAM dashboard-run history and relate live run handles to persisted Claude Code or Codex sessions.

MITAuto-check passed

Install Run History

skills CLI
$ npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill run-history -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hoangsonww/Claude-Code-Agent-Monitor run-history --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ccam-runner/skills/run-history .claude/skills/run-history && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
run-history
GitHub stars
1.1k
Token cost
~255 tokens
SKILL.md length
104 words
Files
2
Skills in repo
78
Repo updated
First seen
Licence
MIT

At a glance

Inspect CCAM dashboard-run history and relate live run handles to persisted Claude Code or Codex sessions.

  • Works in 6 steps: Run ccam run history --limit 100. → Filter by provider, working directory,… → For a live handle, run ccam run get… → …
  • Finding a prior launched task
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Checking whether a run is still attached

What it does

Run History is an agent skill from hoangsonww/Claude-Code-Agent-Monitor. Inspect CCAM dashboard-run history and relate live run handles to persisted Claude Code or Codex sessions. Use when finding a prior launched task, checking whether a run is still attached, reviewing start/end status, or deciding whether to resume, view, or relaunch work.

Its SKILL.md is about 260 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

The repository describes itself as: 🚀 A real-time monitoring dashboard for Claude Code & Codex, built with SQLite3, Node.js, Express, React, Vite, TailwindCSS, & WebSockets. It tracks sessions, agent activity… The licence is MIT.

When your agent uses it

  • Finding a prior launched task
  • Checking whether a run is still attached
  • Reviewing start/end status
  • Deciding whether to resume

Example prompts

  • “/run-history”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Run ccam run history --limit 100.
  2. Filter by provider, working directory, model, status, and session ID.
  3. For a live handle, run ccam run get --envelopes.
  4. For the persisted agent session, use ccam session and the
  5. Distinguish
  6. Recommend resume only when the native session ID is present and the selected

What it can do on your machine

Read from SKILL.md and the folder at commit a06db03. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Run History loads about 255 tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 104 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~255

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hoangsonww/Claude-Code-Agent-Monitor at commit a06db03, republished under its MIT licence (© hoangsonww). 104 words, ~255 tokens.

Download SKILL.mdSave it as .claude/skills/run-history/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
run-history
description
Inspect CCAM dashboard-run history and relate live run handles to persisted Claude Code or Codex sessions. Use when finding a prior launched task, checking whether a run is still attached, reviewing start/end status, or deciding whether to resume, view, or relaunch work.

Run History

  1. Run ccam run history --limit 100.
  2. Filter by provider, working directory, model, status, and session ID.
  3. For a live handle, run ccam run get <id> --envelopes.
  4. For the persisted agent session, use ccam session <session-id> and the session transcript tools.
  5. Distinguish:
    • process still live
    • process completed with usable output
    • process failed
    • history row exists but the in-memory handle was reaped
  6. Recommend resume only when the native session ID is present and the selected provider supports that session.

Return the exact run ID, provider, session ID, working directory, model, timestamps, lifecycle state, and the next safe action.

© hoangsonww, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in plugins/ccam-runner/skills/run-history of hoangsonww/Claude-Code-Agent-Monitor.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit a06db03

Compare with similar skills

Run History next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Run History compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run History this skillhoangsonww/Claude-Code-Agent-Monitor1.1k—~255Automated safety check: PassMIT
Dashboardasgeirtj/system_prompts_leaks69k—~4.1kAutomated safety check: PassCC0-1.0
Error Handlingaffaan-m/ECC277k1 repos~2.7kAutomated safety check: PassMIT
Error Handlingthedaviddias/Front-End-Checklist74k—~416Automated safety check: PassMIT
DashboardInsForge/InsForge13k—~2.3kAutomated safety check: PassApache-2.0
Error Handlingaffaan-m/ECC276k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Dashboard

    asgeirtj/system_prompts_leaks

    Use this for a dashboard, metrics page, KPI tracker, scorecard, data visualization or recurring report: a page or scroll story of charts, numbers and tables of data, whatever the data and wherever…

    69k GitHub stars~4.1k tokensUpdated yesterday
    Data & AnalyticsAuto-check passed
  • Error Handling

    affaan-m/ECC

    Patterns for robust error handling across TypeScript, Python, and Go.

    277k GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed
  • Error Handling

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Implement proper error handling.

    74k GitHub stars~416 tokensUpdated 5 days ago
    DevelopmentAuto-check passed
  • Dashboard

    InsForge/InsForge

    A skill your agent uses when contributing to InsForge's shared dashboard package.

    13k GitHub stars~2.3k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Error Handling

    affaan-m/ECC

    TypeScript、Python、Goにわたる堅牢なエラー処理のパターン。型付きエラー、エラー境界、リトライ、サーキットブレーカー、ユーザー向けエラーメッセージをカバーします。

    276k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Node Inspect Debugger

    openclaw/openclaw

    Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.

    392k GitHub starsUsed in 1 repo~894 tokens
    Frontend & DesignAuto-check passed

More from hoangsonww/Claude-Code-Agent-Monitor

All 78 skills in this repo
  • Version Release

    hoangsonww/Claude-Code-Agent-Monitor

    Choose and apply the correct semantic version bump for this repository.

    1.1k GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Budget Set

    hoangsonww/Claude-Code-Agent-Monitor

    Define a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the Agent Monitor dashboard.

    1.1k GitHub stars~1k tokensUpdated yesterday
    Auto-check passed
  • Cache Efficiency

    hoangsonww/Claude-Code-Agent-Monitor

    Analyze prompt-cache effectiveness for Claude Code usage from the Agent Monitor dashboard — cache hit rate (totalcacheread / (totalcacheread + totalinput)), cachewrite vs cacheread reuse, cache-read…

    1.1k GitHub stars~966 tokensUpdated yesterday
    Auto-check passed
  • Cost Breakdown

    hoangsonww/Claude-Code-Agent-Monitor

    Break down Claude Code costs using the Agent Monitor pricing engine.

    1.1k GitHub stars~845 tokensUpdated yesterday
    Auto-check passed
  • Dag Map

    hoangsonww/Claude-Code-Agent-Monitor

    Render the multi-agent orchestration DAG for a session — parent→child subagent edges, tree depth, and fan-out — from the Agent Monitor workflow intelligence API.

    1.1k GitHub stars~564 tokensUpdated yesterday
    Auto-check passed
  • Dashboard Status

    hoangsonww/Claude-Code-Agent-Monitor

    Quick dashboard health and status overview — checks the Agent Monitor API (port 4820), reports session/agent/event counts from /api/stats, confirms WebSocket connectivity, reads the redacted hook…

    1.1k GitHub stars~600 tokensUpdated yesterday
    Auto-check passed

Questions about Run History

What does Run History do?

Inspect CCAM dashboard-run history and relate live run handles to persisted Claude Code or Codex sessions. Run History is an agent skill from hoangsonww/Claude-Code-Agent-Monitor. Inspect CCAM dashboard-run history and relate live run handles to persisted Claude Code or Codex sessions.

When should I use Run History?

Run History fits situations like: finding a prior launched task; checking whether a run is still attached; reviewing start/end status; deciding whether to resume.

How do I install Run History in Claude Code?

Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill run-history -a claude-code`. Or copy the skill folder (plugins/ccam-runner/skills/run-history in hoangsonww/Claude-Code-Agent-Monitor) into .claude/skills/run-history in your project. Claude Code loads it when a task matches its description.

How do I install Run History in Codex?

Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill run-history -a codex`. Or copy the skill folder (plugins/ccam-runner/skills/run-history in hoangsonww/Claude-Code-Agent-Monitor) into .agents/skills/run-history in your project. Codex loads it when a task matches its description.

Can I use Run History in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill run-history -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-history, .gemini/skills/run-history, .github/skills/run-history and .opencode/skills/run-history in your project.

What does Run History need to run?

SKILL.md names no scripts, command-line tools or credentials: Run History is instructions for the agent only.

Does Run History access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Run History safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Run History use?

Run History is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Run History use?

About 255 tokens (SKILL.md is roughly 1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Run History?

Skills that share tags, products or a category with Run History: Dashboard (asgeirtj/system_prompts_leaks, 69k stars), Error Handling (affaan-m/ECC, 277k stars), Error Handling (thedaviddias/Front-End-Checklist, 74k stars) and Dashboard (InsForge/InsForge, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run History?

hoangsonww (a GitHub user) maintains it in hoangsonww/Claude-Code-Agent-Monitor, which has 1,058 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 10, 2026.

Source: hoangsonww/Claude-Code-Agent-Monitor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.