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/jansenanalytics/claudex/data-padnpx skills add JansenAnalytics/claudex --skill data-padgit clone --depth 1 https://github.com/JansenAnalytics/claudexWhat 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.00045 | $0.00545 |
| Opus 5 | $0.00023 | $0.00272 |
| Sonnet 5 | $0.00009 | $0.00109 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
data-pad 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 2d 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.
What it actually says
Data Pad Skill
Use when: the user provides a CSV, JSON, or NDJSON file and wants analysis, filtering, aggregation, or exploration. Also use when you have structured data from an API and want to query it.
Load data
node ${DATA_PAD_HOME:-$HOME/projects/data-pad}/load.cjs --file <path> [--table name] [--db name] [--overwrite]
node ${DATA_PAD_HOME:-$HOME/projects/data-pad}/load.cjs --file data.csv --table customers --db analysis
Supported formats: .csv, .json, .ndjson
Also supports: --url https://... (fetches JSON from URL)
Run a query
node ${DATA_PAD_HOME:-$HOME/projects/data-pad}/query.cjs "SQL here" [--db name]
node ${DATA_PAD_HOME:-$HOME/projects/data-pad}/query.cjs "SELECT country, SUM(revenue) FROM customers GROUP BY country ORDER BY 2 DESC LIMIT 10"
Explore schema
node ${DATA_PAD_HOME:-$HOME/projects/data-pad}/describe.cjs [--db name]
List all databases
node ${DATA_PAD_HOME:-$HOME/projects/data-pad}/list-dbs.cjs
Export results
node ${DATA_PAD_HOME:-$HOME/projects/data-pad}/export.cjs "SELECT ..." --out results.csv [--db name]
Output formats for query
--csvmachine-readable CSV--jsonJSON array- (default: pretty ASCII table)
Common SQL patterns
-- Top N by value
SELECT name, revenue FROM customers ORDER BY revenue DESC LIMIT 10
-- Aggregation
SELECT country, COUNT(*) as count, AVG(revenue) as avg_rev FROM customers GROUP BY country
-- Filter + count
SELECT COUNT(*) FROM orders WHERE status = 'failed' AND amount > 100
-- Join (if you have multiple tables)
SELECT c.name, SUM(o.amount) FROM customers c JOIN orders o ON c.id = o.customer_id GROUP BY c.id
Databases are stored at
${DATA_PAD_HOME:-$HOME/projects/data-pad}/databases/
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.
- 2d ago First seen · 74 lines · 45 tokens per session scan A b5277ba4f747
data-pad is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 545 once invoked, about $0.0002 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
sq-site-dependabot
Reviews, validates, and safely merges Dependabot pull requests for the sq.io site (site/, Bun lockfile). Use when clearing site dependency PRs, triaging Dependabot failures, or checking Lighthouse impact before merge.
sq-actions-dependabot
Reviews and merges Dependabot pull requests for GitHub Actions (the github-actions ecosystem) that bump uses: pins in .github/workflows/. Use for Dependabot githubactions PRs (branches like dependabot/githubactions/...), not go.mod or site/ Bun PRs.
sq
Guides use of the sq CLI to query SQL databases and tabular files with SLQ (sq's jq-like query language) or native SQL, manage sources, choose output formats, and run inspect, diff, and table commands. Use when the user mentions sq, SLQ, wrangling CSV/Excel/JSON/DB data, cross-source joins, or command-line data…
sq-gomod-dependabot
Reviews and merges Dependabot pull requests for Go modules (gomod) at the sq repo root. Use for dependabot gomod PRs, go.mod/go.sum updates, and Go module security bumps—not site/ Bun PRs.
Workspace Data Analyst
Analyze CSV files in the workspace and summarize insights.
data-analysis
Answer data questions from quick metric lookups to full investigations and stakeholder-ready reports.