export

A command that turns Claude Code session history into a CSV or JSON file. CSV is a table format commonly used in spreadsheets, while JSON is a structured format used by software.

In plain words
What is it for?
Use it to export history for cost or activity analysis, choose CSV or JSON, and redirect the result into a file.
Why use it?
It makes session records easier to inspect, analyse, or use in another tool instead of leaving them only inside the coding-agent interface.

Command

Part of the claudetop plugin — 5 commands shipped together

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/liorwn/claudetop/export
Clone the repo
git clone --depth 1 https://github.com/liorwn/claudetop

Or install claudetop, the plugin that ships this one along with the rest of its 5 commands.

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 122 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.00009 $0.00122
Opus 5 $0.00005 $0.00061
Sonnet 5 $0.00002 $0.00024
Haiku 4.5 $0.00001 $0.00012

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

Security

Grade A, and why

export 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 3d 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.

commands/export.md · 19 lines

What it actually says

claudetop-export

Export session history for analysis in spreadsheets or external tools.

If no format specified, default to csv.

claudetop-stats export $ARGUMENTS

Show the first 10 lines of output. Tell the user they can redirect to a file: claudetop-stats export csv > ~/costs.csv

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. 3d ago First seen · 19 lines · 9 tokens per session scan A 7acdebc20aa1

Subscribe to this mod's changes

export is a command published in the GitHub repository liorwn/claudetop (213 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 122 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.