Agent skill · Audited from source
Data Export
skill · hoangsonww/Claude-Code-Agent-MonitorMIT licenceAudited 16 Oct 2026 · source 1f059c400d07
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 1f059c400d07 and found no filesystem, network or shell access and no hard-coded secrets. What it does: 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.
Cite
Cite this page
ModelsAtlas. “Data Export (hoangsonww/Claude-Code-Agent-Monitor)”. Retrieved 16 Oct 2026. https://modelsatlas.com/skills/hoangsonww/data-export
Trust audit
Audit 0.4.1 · source read 16 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 1f059c400d07 · 16 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherhoangsonww GitHub userOwner of the repository this skill is read from
- Source folderhoangsonww/Claude-Code-Agent-Monitor/plugins/ccam-devtools/skills/data-exportThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict1f059c400d07A new audit runs when the source changes
- Repository statusNot archivedLast push 4 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its 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.
---
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 savingExcerpt, first 2,147 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 1f059c4
git clone https://github.com/hoangsonww/Claude-Code-Agent-Monitor git -C Claude-Code-Agent-Monitor checkout 1f059c400d07
The author documents no install command, so this uses the repository directly. Our verdict covers commit 1f059c400d07 only.
Works in which agents?
What its own text says, not a test
| Agent | Status | More |
|---|---|---|
| Claude Code | Mentioned in its text, not tested | Skills for Claude Code · About Claude Code |
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
1f059c400d07
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/hoangsonww/data-export/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
All data & analysis skills →hoangsonww/Claude-Code-Agent-Monitor
Identify anomalous sessions using Agent Monitor data — cost outliers from the pricing engine, token anomalies (cache miss spikes, compaction baseline surges), unusual event type ratios (PreToolUse/PostToolUse gaps,…
hoangsonww/Claude-Code-Agent-Monitor
Break down Claude Code costs using the Agent Monitor pricing engine. Shows per-model costs (input, output, cache_read, cache_write at $/Mtok rates), per-session costs, daily trends, and compaction baseline token…
hoangsonww/Claude-Code-Agent-Monitor
Generate a daily standup summary from recent Claude Code sessions — completed work grouped by project (cwd), session costs from the pricing engine, tool invocations, error/compaction/APIError events, and turn velocity…
hoangsonww/Claude-Code-Agent-Monitor
Quick dashboard health and status overview — checks the Agent Monitor API (port 4820), reports session/agent/event counts from /api/stats, confirms WebSocket connectivity, reads the redacted hook status returned by…
hoangsonww/Claude-Code-Agent-Monitor
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI.
hoangsonww/Claude-Code-Agent-Monitor
Run comprehensive health checks on the Claude Code Agent Monitor system. Validates dashboard API, database, WebSocket, hooks, and disk usage. Use to verify the monitoring setup is working correctly.
Add this badge to your README
[](https://modelsatlas.com/skills/hoangsonww/data-export/)
<a href="https://modelsatlas.com/skills/hoangsonww/data-export/"><img src="https://modelsatlas.com/skills/hoangsonww/data-export/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about Data Export
What does the Data Export skill do?
Is Data Export safe to install?
What can Data Export access on my machine?
Which assistants does Data Export work with?
How current is this page?
Sources
- github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plug — the audited source at commit 1f059c400d07 and every finding aboveObserved · 16 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the Data Export skill do?
- Is Data Export safe to install?
- What can Data Export access on my machine?