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/danielrosehill/claude-data-analyst-plugin/setup-data-workspacenpx skills add danielrosehill/Claude-Data-Analyst-plugin --skill setup-data-workspacegit clone --depth 1 https://github.com/danielrosehill/Claude-Data-Analyst-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/danielrosehill/claude-data-analyst-plugin/setup-data-workspace)<a href="https://agentmods.dev/skills/danielrosehill/claude-data-analyst-plugin/setup-data-workspace"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-data-analyst-plugin/setup-data-workspace.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00073 | $0.01263 |
| Opus 5 | $0.00036 | $0.00632 |
| Sonnet 5 | $0.00015 | $0.00253 |
| Haiku 4.5 | $0.00007 | $0.00126 |
Grade A, and why
setup-data-workspace 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Data Workspace
Turn a folder of loose data files into a single queryable DuckDB database, and teach future Claude sessions (via CLAUDE.md) how to use it.
DuckDB is the right default here: zero-server, single-file .duckdb database, reads CSV/Parquet/JSON/Excel natively, and every skill in this plugin already assumes duckdb is on PATH.
Inputs
- Target repo (default: current working directory).
- Optional: explicit data directory (default: scan the repo for data files).
- Optional: database filename (default:
data.duckdbat repo root).
Procedure
Step 1 — Discover data
Scan the repo for data files, ignoring .git, node_modules, .venv, __pycache__, dist, build:
find . -type f \( -iname '*.csv' -o -iname '*.tsv' -o -iname '*.parquet' \
-o -iname '*.json' -o -iname '*.jsonl' -o -iname '*.ndjson' \
-o -iname '*.xlsx' -o -iname '*.xls' \) \
-not -path '*/\.*' -not -path '*/node_modules/*' -not -path '*/\.venv/*'
Report what was found: file count, total size, formats, any obvious groupings (e.g. all CSVs in data/raw/). If nothing is found, ask the user where the data lives.
Step 2 — Confirm scope
Before loading, show the user the file list and confirm:
- Which files to load (default: all discovered).
- Table naming — default: sanitised filename stem (e.g.
sales_2024.csv→sales_2024). Flag collisions. - Whether to load as views (re-read source on every query, always fresh) or tables (materialised, faster but frozen). Default: views for CSV/JSON, tables for Excel (xlsx reading is slow).
Step 3 — Create the database
Generate a loader SQL script at scripts/load_data.sql (create scripts/ if needed). Example shape:
-- Auto-generated by setup-data-workspace
-- Re-run with: duckdb data.duckdb < scripts/load_data.sql
INSTALL excel; LOAD excel; -- only if xlsx present
CREATE OR REPLACE VIEW sales_2024 AS SELECT * FROM read_csv_auto('data/raw/sales_2024.csv');
CREATE OR REPLACE VIEW customers AS SELECT * FROM read_csv_auto('data/raw/customers.csv');
CREATE OR REPLACE TABLE budget AS SELECT * FROM read_xlsx('data/raw/budget.xlsx');
-- ...
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.
- 4d ago First seen · 107 lines · 73 tokens per session scan A 5d6b8fc38adb
setup-data-workspace is a skill published in the GitHub repository danielrosehill/Claude-Data-Analyst-plugin (11 stars, last pushed 4mo ago), licensed MIT. It adds 73 tokens to every session and 1,263 once invoked, about $0.0004 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.
Other skills, from other repositories
cerna-analysis
Use when building a ceRNA regulatory network from a key gene list by combining bundled miRNA-mRNA and miRNA-lncRNA database files, with flat-file CSV exports and PDF visualization in a single output directory. NOT for: differential expression, single-cell analysis, enrichment analysis, or workflows without a key gene…
lncrna-regulatory-network-construction-analysis
Use this bioinformatics data analysis skill to construct a database-driven lncRNA-mRNA regulatory network from target lncRNA and/or gene lists by projecting shared miRNA evidence from local ceRNA reference tables. It does not infer networks from expression matrices.
data-analysis
Answer data questions from quick metric lookups to full investigations and stakeholder-ready reports.
reporting-guideline-compliance-checker
Checks biomedical manuscripts against reporting guidelines such as CONSORT, STROBE, PRISMA, and TRIPOD to identify missing or weak reporting elements before submission or revision.
methods-section-writer
Turns your protocol and analysis workflow into publication-ready Methods text. Use when writing or revising the Methods section of a biomedical manuscript, ensuring it complies with reporting guidelines (CONSORT, STROBE, PRISMA, TRIPOD), matches what is in the Results section, and satisfies journal-specific word…
fetch-data
取数 / 查数据 / 拉数据 / 跑 SQL。把自然语言取数需求转为 SQL,经数据湖仓执行后返回查询结果供下游分析。任何需要业务数据的任务在工作区缺少对应文件时都必须先调用此技能——覆盖 BI 业务分析、留存 / 转化 / 同期群分析、数据探索 EDA、统计建模、定量计算、元数据查询、数据查询。命中任一即触发:(1) 直接索要指标或记录,如「DAU 多少」「上月销售额」「3 月留存率」「这个客户的订单」;(2) 取数口语,如「查 / 查一下 / 取一下 / 拉一下 / 抓数据 / 找数据 / 搜数据 / 跑 SQL / 写 SQL / 导出 / 缺数据 / 没数据 / 数据不够」;(3) 涉及数据来源,如「从语义层 / 数据湖仓…