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.
npx agentmods add skills/tsmztech/claude-code-plugins/data-exportnpx skills add tsmztech/claude-code-plugins --skill data-exportgit clone --depth 1 https://github.com/tsmztech/claude-code-pluginsWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00094 | $0.01719 |
| Opus 5 | $0.00047 | $0.00860 |
| Sonnet 5 | $0.00019 | $0.00344 |
| Haiku 4.5 | $0.00009 | $0.00172 |
Grade A, and why
data-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 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Export
Export Salesforce query results to a local CSV or JSON file. Handles automatic pagination to fetch all records and supports Bulk API 2.0 for very large datasets.
Prerequisites
You must be authenticated to a Salesforce org before exporting data. If not authenticated, run the authentication script first.
Authentication
If the user is not authenticated or gets an auth error, run the authentication script:
node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --status
To authenticate interactively (opens browser):
node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --alias <alias>
To authenticate to a sandbox:
node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --alias <alias> --instance-url https://test.salesforce.com
See scripts/sf-auth.js --help for all authentication options.
Usage
node ${CLAUDE_PLUGIN_ROOT}/skills/data-export/scripts/export.js "<SOQL>" --output <file-path> [options]
Options
| Option | Short | Description | Default |
|---|---|---|---|
--output |
-f |
Output file path (required) | — |
--format |
csv or json |
auto-detected from file extension | |
--target-org |
-o |
Target org alias or username | default org |
--all-rows |
Include deleted/archived records | false | |
--bulk |
Use Bulk API 2.0 for large exports | false | |
--wait |
-w |
Minutes to wait for bulk job (default: 10) | 10 |
--json |
Print export metadata as JSON to stdout | — | |
--help |
-h |
Show help | — |
Examples
# Export accounts to CSV
node ${CLAUDE_PLUGIN_ROOT}/skills/data-export/scripts/export.js "SELECT Id, Name, Industry FROM Account" --output accounts.csv
# Export to JSON (auto-detected from extension)
node ${CLAUDE_PLUGIN_ROOT}/skills/data-export/scripts/export.js "SELECT Id, Name, Email FROM Contact" --output contacts.json
# Export with specific format override
node ${CLAUDE_PLUGIN_ROOT}/skills/data-export/scripts/export.js "SELECT Id, Name FROM Account" --output data.txt --format csv
# Export from a specific org
node ${CLAUDE_PLUGIN_ROOT}/skills/data-export/scripts/export.js "SELECT Id, Name FROM Account" -f accounts.csv -o myDevOrg
# Include deleted/archived records
node ${CLAUDE_PLUGIN_ROOT}/skills/data-export/scripts/export.js "SELECT Id, Name FROM Account" -f accounts.csv --all-rows
# Bulk export for large datasets (100k+ records)
node ${CLAUDE_PLUGIN_ROOT}/skills/data-export/scripts/export.js "SELECT Id, Name, Email FROM Lead" -f leads.csv --bulk
# Bulk export with longer wait time
node ${CLAUDE_PLUGIN_ROOT}/skills/data-export/scripts/export.js "SELECT Id, Name FROM Contact" -f contacts.csv --bulk --wait 20
# Export with dot notation (parent fields)
node ${CLAUDE_PLUGIN_ROOT}/skills/data-export/scripts/export.js "SELECT Id, Name, Account.Name, Account.Industry FROM Contact" -f contacts-with-accounts.csv
# Export with metadata output as JSON
node ${CLAUDE_PLUGIN_ROOT}/skills/data-export/scripts/export.js "SELECT Id, Name FROM Account" -f accounts.csv --json
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 147 lines · 94 tokens per session scan A 5cd8ae6b4c48
data-export is a skill published in the GitHub repository tsmztech/claude-code-plugins (2 stars, last pushed 6mo ago), licensed MIT. It adds 94 tokens to every session and 1,719 once invoked, about $0.0005 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…