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/letitbk/claude-academic-setup/datachecknpx skills add letitbk/claude-academic-setup --skill datacheckgit clone --depth 1 https://github.com/letitbk/claude-academic-setupWrote 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/letitbk/claude-academic-setup/datacheck)<a href="https://agentmods.dev/skills/letitbk/claude-academic-setup/datacheck"><img src="https://agentmods.dev/badge/skills/letitbk/claude-academic-setup/datacheck.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.1 | $0.00048 | $0.01404 |
| Opus 5 | $0.00024 | $0.00702 |
| Sonnet 5 | $0.00010 | $0.00281 |
| Haiku 4.5 | $0.00005 | $0.00140 |
Grade A, and why
datacheck 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 6d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Check
Inspect and validate a data file before analysis. Report findings with suggested fixes. Do not auto-fix.
When to Use
- Before any analysis or visualization on a new data file
- When parsing errors or unexpected values appear
- When switching to a different dataset mid-session
- User says "check", "inspect", "what's in this", "profile" a data file
When NOT to Use
- File has already been checked in this session and nothing changed
- User just wants to read a specific value (use Read tool directly)
Workflow
Step 1: Raw File Inspection
Before loading into R/Stata, check the raw file:
file <filename> # encoding detection
head -c 500 <filename> | cat -v # hidden chars: ^M (CR), BOM, non-UTF8
wc -l <filename> # row count sanity check
head -3 <filename> # peek at delimiter and header
Flag these issues:
| Symptom | Meaning |
|---|---|
^M at line ends |
Classic Mac \r or Windows \r\n line endings |
\xEF\xBB\xBF at start |
UTF-8 BOM marker |
Only 1 line from wc -l |
Entire file on one line (wrong line endings) |
| Mixed delimiters | Inconsistent separator characters |
Step 2: Load and Summarize
R-first. Use Stata only when the file is .dta and project context is Stata-based.
For CSV files:
df <- read.csv("file.csv", stringsAsFactors = FALSE)
For Stata .dta files:
library(haven)
df <- read_dta("file.dta")
Report this table:
| Item | Value |
|---|---|
| Dimensions | rows x cols |
| Column names | list all |
| Column types | numeric, character, factor, labelled, date |
| Total missing | count and % |
Then per column:
Column Type Missing Unique Example Values
─────────────────────────────────────────────────────────────
age numeric 12 (2%) 45 18, 25, 34, 67, 89
gender labelled 0 (0%) 3 1=Male, 2=Female, 3=Other
weight_var numeric 0 (0%) 847 0.23, 1.05, 2.11
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.
- 6d ago First seen · 146 lines · 48 tokens per session scan A cbb720b7185d
datacheck is a skill published in the GitHub repository letitbk/claude-academic-setup (43 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 1,404 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-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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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-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…