list

A command for listing saved conversation files with their basic metadata.

In plain words
What is it for?
It is for viewing conversations sorted by date, size, or name, with optional filtering by Markdown, text, or HTML format.
Why use it?
It makes saved chats easier to find than browsing the save directory manually.

Command

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/dropfan/claude-code-plugins/list
Clone the repo
git clone --depth 1 https://github.com/DropFan/claude-code-plugins
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 682 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.00005 $0.00682
Opus 5 $0.00003 $0.00341
Sonnet 5 $0.00001 $0.00136
Haiku 4.5 $0.00001 $0.00068

Measured yesterday against content hash 3605ac07b378, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

list 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 yesterday.

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/chat-saver/commands/list.md · 77 lines

How it starts

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

Context

  • Working directory: !pwd
  • Current date: !date '+%Y-%m-%d %H:%M'
  • Plugin root: ${CLAUDE_PLUGIN_ROOT}

Task

List all saved conversation files in the save directory. Display them in a formatted table with metadata.

User arguments: $ARGUMENTS

Step 0: Load Settings

Load settings from .claude/chat-saver.local.md following ${CLAUDE_PLUGIN_ROOT}/skills/conversation-export/references/settings-loading.md. Extract: save_dir.

Step 1: Parse Arguments

Parse optional arguments from $ARGUMENTS:

  • --sort — Sort order: date (default, newest first), size (largest first), or name (alphabetical)
  • --format — Filter by format: md, txt, or html. If omitted, show all formats

Step 2: Scan Directory

  1. Use Glob to find all files in <save_dir>:
    <save_dir>/*.md
    <save_dir>/*.txt
    <save_dir>/*.html
    
  2. If no files are found, inform the user that no saved conversations exist and exit
  3. If --format filter is set, only include files with the matching extension

Step 3: Extract Metadata

For each file found:

  1. Extract the date from the filename prefix (YYYY-MM-DD)
  2. Extract the topic from the filename (between date and extension)
  3. Determine the format from the extension
  4. Get the line count using wc -l
  5. Get the file size using ls -lh

Step 4: Display Table

Present the results as a formatted table:

Saved Conversations (<save_dir>)
Showing N files, sorted by <sort_order>

  #  │ Date       │ Topic                │ Format │ Lines │ Size
 ────┼────────────┼──────────────────────┼────────┼───────┼──────
  1  │ 2024-01-15 │ auth-implementation  │ md     │  156  │ 12K
  2  │ 2024-01-14 │ fix-login-timeout    │ md     │   89  │  7K
  3  │ 2024-01-13 │ db-schema-design     │ html   │  234  │ 18K

Step 5: Follow-up

After displaying the table, ask the user what they'd like to do next:

Use AskUserQuestion with options:

  • Read — Open and display a specific file
  • Search — Search within saved conversations
  • Clean — Remove old or unwanted files
  • Done — No further action

Read the full file on GitHub · 77 lines

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. yesterday First seen · 77 lines · 5 tokens per session scan A 3605ac07b378

Subscribe to this mod's changes

list is a command published in the GitHub repository DropFan/claude-code-plugins (7 stars, last pushed 26d ago), licensed MIT. It adds 5 tokens to every session and 682 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-31.