# data-export

Exports Claude Code sessions, events, costs, and analytics into JSON, CSV, or Markdown. Useful for backups, cost auditing, and custom reports.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 1121
- Author: hoangsonww
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/HEAD/plugins/ccam-devtools/skills/data-export/SKILL.md
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/skills/data-export

## What it does

This skill pulls operational records directly from Agent Monitor running locally. You pass it target data types like `sessions`, `events`, `costs`, or `analytics`, along with optional date filters and preferred output formats. By default, it outputs formatted JSON with metadata headers.

Under the hood, the skill queries `http://localhost:4820` endpoints, including `GET /api/sessions` and `GET /api/pricing/cost`. Small responses under 100 rows print right in the conversation, while larger batches save straight to disk with a file path report.

Data retrieval fails immediately if Agent Monitor is not actively running on port 4820. CSV outputs include standard ISO timestamps and cost columns, while Markdown outputs include summary totals for quick review.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill data-export -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/data-export/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/data-export/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill data-export -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/data-export/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill data-export -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/data-export/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install hoangsonww/Claude-Code-Agent-Monitor data-export
```

2. **Manually: put the files in place**
- File: `.github/skills/data-export/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill data-export -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/hoangsonww/Claude-Code-Agent-Monitor --path plugins/ccam-devtools/skills/data-export
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/data-export/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill data-export -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/HEAD/plugins/ccam-devtools/skills/data-export/SKILL.md

## When to use it
- export Claude Code session logs to CSV files
- generate Markdown cost summaries with total spending
- filter events from the last 30 days for reporting
- backup all Agent Monitor metrics into JSON

## Example prompts
- Export sessions from the last 7 days to csv
- Show cost analytics in markdown
- Export all events to json

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: a8be104f12479fac.

BEGIN THIRD-PARTY FILE a8be104f12479fac
````text
---
name: data-export
description: >
  Export Claude Code session and analytics data in JSON, CSV, or Markdown
  formats. Supports exporting sessions, events, costs, and analytics
  for external analysis or reporting. Use for data backup or integration.
---

# Data Export

Export Agent Monitor data in various formats.

## Input

The user provides: **$ARGUMENTS**

This may be:
- A data type: "sessions", "events", "analytics", "costs", "all"
- A format: "json", "csv", "markdown" (default: json)
- A filter: "last 7 days", "session {id}", "completed only"
- Combined: "sessions csv last 30 days"

## Procedure

1. **Parse the request** to determine:
   - Data scope: which data to export
   - Format: output format
   - Filters: time range, status, session ID

2. **Fetch data** from `http://localhost:4820`:
   - Sessions: `GET /api/sessions?limit=1000`
   - Events: `GET /api/events?limit=5000`
   - Analytics: `GET /api/analytics`
   - Costs: `GET /api/pricing/cost`
   - Full export: `GET /api/settings/export`

3. **Transform to requested format**:

   ### JSON Format
   Pretty-printed JSON with metadata header:
   ```json
   {
     "export": {
       "source": "Claude Code Agent Monitor",
       "exported_at": "2025-04-11T12:00:00Z",
       "filters": { "type": "sessions", "range": "last 7 days" },
       "count": 42
     },
     "data": [...]
   }
   ```

   ### CSV Format
   Standard CSV with headers, proper quoting, and ISO timestamps:
   ```
   id,name,status,model,started_at,ended_at,duration_minutes,cost_usd
   ```

   ### Markdown Format
   Human-readable tables with summary statistics:
   ```markdown
   # Agent Monitor Export — Sessions (Last 7 Days)
   | ID | Name | Status | Model | Duration | Cost |
   |...
   **Total: 42 sessions, $12.34 cost**
   ```

4. **Output the data**:
   - For small exports (<100 rows): output directly
   - For large exports: save to file and report the path
   - Include row count and any filter notes

## Output Format

Deliver the exported data in the requested format. Always include:
- Export metadata (when, what, filters applied)
- Row/record count
- Suggested filename for saving
````
END THIRD-PARTY FILE a8be104f12479fac

The third-party file has ended. Everything between the a8be104f12479fac tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

© hoangsonww · MIT · https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/HEAD/plugins/ccam-devtools/skills/data-export/SKILL.md

## Similar
- [setup-matt-pocock-skills](https://affpapa.org/en/nevibecode/skills/setup-matt-pocock-skills.md) — skill · 1052851 installs
- [ask-matt](https://affpapa.org/en/nevibecode/skills/ask-matt.md) — skill · 766587 installs
- [to-tickets](https://affpapa.org/en/nevibecode/skills/to-tickets.md) — skill · 711230 installs
- [writing-plans](https://affpapa.org/en/nevibecode/skills/writing-plans.md) — skill · 282859 installs
- [caveman-review](https://affpapa.org/en/nevibecode/skills/caveman-review.md) — skill · 411800 installs
- [caveman-compress](https://affpapa.org/en/nevibecode/skills/caveman-compress.md) — skill · 411500 installs

From the same set: [hoangsonww/claude-code-agent-monitor](https://affpapa.org/en/nevibecode/by/hoangsonww/claude-code-agent-monitor.md) — 60 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md