Agent Session Monitor
higress-group/higress
Real-time agent conversation monitoring - monitors Higress access logs, aggregates conversations by session, tracks token usage.
Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before…
MITAuto-check passed
Install Session Cleanup
$ npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-cleanup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hoangsonww/Claude-Code-Agent-Monitor session-cleanup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-sessions/skills/session-cleanup .claude/skills/session-cleanup && rm -rf skills-srcUse ~/.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/
Install the "session-cleanup" agent skill from https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-sessions/skills/session-cleanup into .claude/skills/session-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-cleanup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-sessions/skills/session-cleanupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-cleanup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hoangsonww/Claude-Code-Agent-Monitor session-cleanup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ccam-sessions/skills/session-cleanup .agents/skills/session-cleanup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "session-cleanup" agent skill from https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-sessions/skills/session-cleanup into .agents/skills/session-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-cleanup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-cleanup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hoangsonww/Claude-Code-Agent-Monitor session-cleanup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ccam-sessions/skills/session-cleanup .cursor/skills/session-cleanup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "session-cleanup" agent skill from https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-sessions/skills/session-cleanup into .cursor/skills/session-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-cleanup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git --path plugins/ccam-sessions/skills/session-cleanup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-cleanup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hoangsonww/Claude-Code-Agent-Monitor session-cleanup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ccam-sessions/skills/session-cleanup .gemini/skills/session-cleanup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "session-cleanup" agent skill from https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-sessions/skills/session-cleanup into .gemini/skills/session-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-cleanup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hoangsonww/Claude-Code-Agent-Monitor session-cleanupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-cleanup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ccam-sessions/skills/session-cleanup .github/skills/session-cleanup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "session-cleanup" agent skill from https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-sessions/skills/session-cleanup into .github/skills/session-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-cleanup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-cleanup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hoangsonww/Claude-Code-Agent-Monitor session-cleanup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ccam-sessions/skills/session-cleanup .opencode/skills/session-cleanup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "session-cleanup" agent skill from https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-sessions/skills/session-cleanup into .opencode/skills/session-cleanup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-cleanup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
session-cleanup- GitHub stars
- 1.1k
- Token cost
- ~834 tokens
- SKILL.md length
- 386 words
- Files
- 2
- Skills in repo
- 78
- Repo updated
- First seen
- Licence
- MIT
At a glance
Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before…
- Works in 5 steps: Baseline → Identify candidates → Preview table (ALWAYS shown) → …
- Tidying the monitoring database
- SKILL.md covers Input, Data Sources, Report Sections and Output, plus 1 more section
- Calls npm
What it does
Session Cleanup is an agent skill from hoangsonww/Claude-Code-Agent-Monitor. Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before anything is deleted. Cleanup permanently deletes data, so this skill previews first and requires explicit user confirmation. Use when tidying the monitoring database.
Its SKILL.md is about 830 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
- Tidying the monitoring database
Example prompts
- “/session-cleanup”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e0f4a1a. 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
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
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
Session Cleanup loads about 834 tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 386 words of instructions outside code blocks.
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 e0f4a1a, republished under its MIT licence (© hoangsonww). 386 words, ~834 tokens.
Download SKILL.mdSave it as
.claude/skills/session-cleanup/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- session-cleanup
- description
- Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before anything is deleted. Cleanup permanently deletes data, so this skill previews first and requires explicit user confirmation. Use when tidying the monitoring database.
Session Cleanup
Find prune-worthy sessions and explain cleanup — preview first, delete only on explicit confirmation.
Input
The user provides: $ARGUMENTS
- Empty /
preview→ only show what would be removed (the safe default). confirm→ the user has reviewed the preview and explicitly authorizes deletion.- An optional staleness threshold (e.g.
older than 7d) for what counts as stale.
Data Sources
| Endpoint | Returns |
|---|---|
GET /api/sessions?limit=N | session list: id, status, model, cwd, started_at, ended_at, cost, metadata (turn_count, total_turn_duration_ms) |
GET /api/stats | totals: total_sessions, active_sessions, total_events, events_today, sessions_by_status, agents_by_status |
POST /api/settings/cleanup | runs the cleanup routine and returns what was removed — DESTRUCTIVE, only after confirmation |
Report Sections
1. Baseline
GET /api/stats — record total_sessions, sessions_by_status, total_events. This is
the before-state to compare against.
2. Identify candidates
GET /api/sessions?limit=1000. Flag sessions that are:
- Empty — zero events and
turn_count0 / null andcost0 (started but never did anything). - Stale active —
statusactive/working but last activity older than the threshold (default 24h), i.e. never cleanly stopped. - Truncated — no
ended_atand no recent events.
3. Preview table (ALWAYS shown)
List every candidate with the reason it qualifies. State the total count and confirm that nothing has been deleted yet.
4. Explain the endpoint
Describe POST /api/settings/cleanup: it prunes empty / orphaned sessions and their
dangling events server-side and returns a summary of removed rows. Make clear this
is permanent and not reversible from the dashboard.
Show full SKILL.md (164 more words)Show less
5. Execute only on confirmation
If — and only if — $ARGUMENTS is confirm (or the user has explicitly approved
this run), call POST /api/settings/cleanup, then re-read /api/stats and report
the before → after delta. Otherwise stop after the preview and tell the user to
re-run with confirm.
Output
A preview Markdown table: id (short) | status | reason | cwd basename | started_at | cost,
then a one-line count and the explicit "nothing deleted — re-run with confirm to
proceed" notice. On a confirmed run, add a before → after summary using ▲/▼ on the
counts. Currency as USD to 4 decimal places.
Safety
- This is the ONLY skill in the plugin that mutates data, and only via the one documented endpoint.
- NEVER call
POST /api/settings/cleanupwithout an explicitconfirmfrom the user in this turn — previewing is the default. - Never widen scope to
POST /api/settings/clear-dataor any other destructive endpoint; cleanup of stale/empty sessions only. - If the dashboard is unreachable, tell the user to start it with
npm startfrom the repo root.
© 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-sessions/skills/session-cleanup of hoangsonww/Claude-Code-Agent-Monitor.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit e0f4a1a
Compare with similar skills
Session Cleanup 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Session Cleanup this skillhoangsonww/Claude-Code-Agent-Monitor | 1.1k | — | ~834 | Automated safety check: Pass | MIT | |
| Agent Session Monitorhigress-group/higress | 9.5k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Session Handoffsickn33/agentic-awesome-skills | 47k | — | ~1.8k | Automated safety check: Notes | MIT | |
| Cleanupsimstudioai/sim | 30k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Sessionanthropics/claude-for-legal | 9.6k | 3 repos | ~478 | Automated safety check: Pass | Apache-2.0 | |
| Session History Searchslopus/happy | 24k | — | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
Session Handoff
sickn33/agentic-awesome-skills
A skill your agent uses when context approaches capacity, before /clear or /compact, when switching tasks, or when ending a coding session: produces a structured handoff artifact for the next session.
Cleanup
simstudioai/sim
Run all code quality skills — effects, memo, callbacks, state, React Query, emcn design review, url-state, comments, and test-audit — analyzing in parallel, then applying fixes sequentially
- Official
Session
anthropics/claude-for-legal
Run a focused N-question study session on a subject — MBE, essay, or flashcards.
Session History Search
slopus/happy
Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.
- Official
Qdrant Monitoring
github/awesome-copilot
Guides Qdrant monitoring and observability setup. An agent skill from github/awesome-copilot.
More from hoangsonww/Claude-Code-Agent-Monitor
All 78 skills in this repoBudget 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.
Version Release
hoangsonww/Claude-Code-Agent-Monitor
Choose and apply the correct semantic version bump for this repository.
Cost Breakdown
hoangsonww/Claude-Code-Agent-Monitor
Break down Claude Code costs using the Agent Monitor pricing engine.
File Headers
hoangsonww/Claude-Code-Agent-Monitor
MANDATORY for every coding agent (Claude Code, Codex, or any other) on every change-set — every applicable source file the agent creates or updates MUST start with the project's copyright/authorship…
Hook Diagnostics
hoangsonww/Claude-Code-Agent-Monitor
Diagnose Claude Code hook installation, delivery, and ingestion issues.
Memory Review
hoangsonww/Claude-Code-Agent-Monitor
Review the file-based memory store via the Agent Monitor Config Explorer API: the user and project CLAUDE.md plus per-project auto-memory files under ~/.claude/projects/<slug/memory/.md.
Questions about Session Cleanup
What does Session Cleanup do?
Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before…. Session Cleanup is an agent skill from hoangsonww/Claude-Code-Agent-Monitor. Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before anything is deleted.
When should I use Session Cleanup?
Session Cleanup fits situations like: tidying the monitoring database.
How do I install Session Cleanup in Claude Code?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-cleanup -a claude-code`. Or copy the skill folder (plugins/ccam-sessions/skills/session-cleanup in hoangsonww/Claude-Code-Agent-Monitor) into .claude/skills/session-cleanup in your project. Claude Code loads it when a task matches its description.
How do I install Session Cleanup in Codex?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-cleanup -a codex`. Or copy the skill folder (plugins/ccam-sessions/skills/session-cleanup in hoangsonww/Claude-Code-Agent-Monitor) into .agents/skills/session-cleanup in your project. Codex loads it when a task matches its description.
Can I use Session Cleanup 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 session-cleanup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/session-cleanup, .gemini/skills/session-cleanup, .github/skills/session-cleanup and .opencode/skills/session-cleanup in your project.
What does Session Cleanup need to run?
Going by SKILL.md and its folder, Session Cleanup needs the command-line tools its instructions call (npm).
Does Session Cleanup access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Session Cleanup 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 Session Cleanup use?
Session Cleanup 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 Session Cleanup use?
About 834 tokens (SKILL.md is roughly 3.3k 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 Session Cleanup?
Skills that share tags, products or a category with Session Cleanup: Agent Session Monitor (higress-group/higress, 9.5k stars), Session Handoff (sickn33/agentic-awesome-skills, 47k stars), Cleanup (simstudioai/sim, 30k stars) and Session (anthropics/claude-for-legal, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Session Cleanup?
hoangsonww (a GitHub user) maintains it in hoangsonww/Claude-Code-Agent-Monitor, which has 1,052 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 6, 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.