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 brycewang-stanford/Auto-Empirical-Research-Skills --skill stata-data-cleaninggit clone --depth 1 https://github.com/brycewang-stanford/Auto-Empirical-Research-SkillsWrote 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/brycewang-stanford/auto-empirical-research-skills/stata-data-cleaning)<a href="https://agentmods.dev/skills/brycewang-stanford/auto-empirical-research-skills/stata-data-cleaning"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/auto-empirical-research-skills/stata-data-cleaning/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/brycewang-stanford/auto-empirical-research-skills/stata-data-cleaning"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/auto-empirical-research-skills/stata-data-cleaning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 124 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- high Memory Poisoning · line 125 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
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.00017 | $0.01652 |
| Opus 5 | $0.00009 | $0.00826 |
| Sonnet 5 | $0.00003 | $0.00330 |
| Haiku 4.5 | $0.00002 | $0.00165 |
Grade A, and why
stata-data-cleaning 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 13d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 13d ago First seen · 258 lines · 17 tokens per session scan A 32abec5b70d0
stata-data-cleaning is a skill published in the GitHub repository brycewang-stanford/Auto-Empirical-Research-Skills (3,759 stars, last pushed 5d ago), with no licence file. It adds 17 tokens to every session and 1,652 once invoked, about $0.0001 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
stata-data-cleaning
Clean and transform messy data in Stata with reproducible workflows.
stata-data-cleaning
Clean and transform messy data in Stata with reproducible workflows.
fin-data-acquisition
A data-preparation workflow for financial research. It reads variable definitions from a completed research design and produces data-acquisition work plus executable Python or Stata regression scripts.
gl-paper-replication
Use when helping a user lightly replicate and learn from an empirical economics, management, finance, or accounting paper from public paper materials, create a clean replication project structure, extract variables/data/models, draft basic Stata replication steps, explain code and tables, record reproducible outputs…
stata-data-cleaning
Generates rigorous, reproducible Stata data-cleaning workflows that follow World Bank DIME Analytics conventions (iefieldkit, ietoolkit, iefolder DataWork structure, ieboilstart, iecodebook, ieduplicates, iecompdup, extended missing values, master datasets, encryption for PII, dynamic absolute paths). Defaults to…
data-management-plan
Draft a funder-compliant Data Management Plan (NSF DMP, NIH DMS Policy 2023, ERC, Horizon Europe) by composing the confidential-data and environment-capture primitives. Sections cover data description, formats/metadata, storage/backup, access/sharing, preservation/archiving, and roles. Use when user says "data…