agentmods.dev

sessions

Commands for listing and managing Claude Code sessions, which are saved coding-agent conversations grouped by project. They can show projects and sessions, open a web manager, rename sessions, and clean up or delete them.

In plain words
What is it for?
Use them to list project sessions, start the session-management web interface, preview cleanup, delete sessions, or rename a session.
Why use it?
They provide a way to find old sessions and remove invalid, empty, or unwanted session records.

Command

22 2d ago A scan 6 tokens original MIT
View the source file es6kr/claude-code-sessions
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.

agentmods
npx agentmods add commands/es6kr/claude-code-sessions/sessions
Clone the repo
git clone --depth 1 https://github.com/es6kr/claude-code-sessions
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 361 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00006 $0.00361
Opus 5 $0.00003 $0.00180
Sonnet 5 $0.00001 $0.00072
Haiku 4.5 $0.00001 $0.00036

Measured 2d ago against content hash 5a9291a9a1f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sessions 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 2d 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.

plugins/claude-sessions/commands/sessions.md · 40 lines

What it actually says

Session Management

Use the claude-sessions-mcp MCP server tools to help the user manage their Claude Code sessions.

Available Operations

  1. List Projects: Show all projects with session counts

    • Use mcp__claude-sessions-mcp__list_projects tool

  2. List Sessions: Show sessions in a specific project

    • Use mcp__claude-sessions-mcp__list_sessions tool with project_name

  3. Start Web GUI: Open the session management web interface

    • Use mcp__claude-sessions-mcp__start_gui tool
    • Default port: 5173

  4. Cleanup Sessions: Remove empty and invalid sessions

    • First use mcp__claude-sessions-mcp__preview_cleanup to show what will be deleted
    • Then use mcp__claude-sessions-mcp__clear_sessions to perform cleanup

  5. Rename Session: Change a session's title

    • Use mcp__claude-sessions-mcp__rename_session tool

  6. Delete Session: Remove a specific session

    • Use mcp__claude-sessions-mcp__delete_session tool

Usage

Ask the user what they want to do:

  • "List my projects" → list_projects
  • "Show sessions for [project]" → list_sessions
  • "Open session manager" → start_gui
  • "Clean up sessions" → preview_cleanup, then clear_sessions
  • "Rename session [id] to [title]" → rename_session
  • "Delete session [id]" → delete_session
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. 2d ago First seen · 40 lines · 6 tokens per session scan A 5a9291a9a1f4

Subscribe to this mod's changes

sessions is a command published in the GitHub repository es6kr/claude-code-sessions (22 stars, last pushed 2d ago), licensed MIT. It adds 6 tokens to every session and 361 once invoked, about $0.0000 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-08-30.

Related

Other commands, from other repositories

git

Git operations with intelligent commit messages and workflow optimization.

SuperClaude-Org/SuperClaude_Framework · 11 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

constitution

Create or update the project constitution from interactive or provided principle inputs.

github/spec-kit · 13 tokens