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 skills add jezweb/vite-flare-starter --skill csv-analysegit clone --depth 1 https://github.com/jezweb/vite-flare-starterWrote 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/jezweb/vite-flare-starter/csv-analyse)<a href="https://agentmods.dev/skills/jezweb/vite-flare-starter/csv-analyse"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/csv-analyse.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00057 | $0.00559 |
| Opus 5 | $0.00028 | $0.00280 |
| Sonnet 5 | $0.00011 | $0.00112 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
csv-analyse 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 8d 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
CSV analyse
When to use
The user has a CSV file (uploaded, written to the filesystem, or inline) and wants a structured summary or statistical analysis.
Examples:
- "Summarise sales.csv"
- "What columns are in this file and what do they contain?"
- "Give me descriptive stats for the numeric columns"
- "Count missing values per column"
Steps
-
Locate the CSV. If the user mentioned a filename, call
fs_listandfs_readunderuploads/or their chosen folder to get the content as a string. If the content is in a previous tool result or an attachment, pass it directly asstdin. -
Run the bundled analyser. Call:
run_skill_script({ name: "csv-analyse", path: "scripts/analyse.py", stdin: <the CSV content as a string> })The script reads stdin, uses pandas to profile the data, and prints a JSON report to stdout.
-
Parse the JSON. The stdout is a single JSON object with keys:
shape,columns,dtypes,missing,numeric_summary,categorical_summary,head. Show the user the bits they asked for — don't dump the whole thing unless they asked for "everything". -
Offer follow-ups. Use
offer_choiceswith 3-5 relevant next steps, e.g.:- "Plot the distribution of [numeric column]"
- "Filter rows where [condition]"
- "Export the summary to a Word document"
- "Correlate these columns"
Style
- Present the shape (rows × cols) first — it's the most useful single fact.
- Show missing-value percentages only where > 0.
- Round numeric summaries to 3 significant figures.
- If the file is big (>10k rows), mention that analysis used the full file, not a sample.
What not to do
- Don't guess column meanings. If a column name is ambiguous, ask the user.
- Don't dump the full CSV back in the chat. The user already has it.
- Don't run the analysis if the input looks like it's not a CSV (check for delimiters in the first line). Ask for clarification instead.
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.
- 8d ago First seen · 52 lines · 57 tokens per session scan A b45be4c4a275
csv-analyse is a skill published in the GitHub repository jezweb/vite-flare-starter (48 stars, last pushed 13d ago), licensed MIT. It adds 57 tokens to every session and 559 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…