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 kennethkhoocy/applied-micro-skills --skill statagit clone --depth 1 https://github.com/kennethkhoocy/applied-micro-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/kennethkhoocy/applied-micro-skills/stata)<a href="https://agentmods.dev/skills/kennethkhoocy/applied-micro-skills/stata"><img src="https://agentmods.dev/badge/skills/kennethkhoocy/applied-micro-skills/stata/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/kennethkhoocy/applied-micro-skills/stata"><img src="https://agentmods.dev/badge/skills/kennethkhoocy/applied-micro-skills/stata.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Rogue Agent · line 20 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00165 | $0.02492 |
| Opus 5.5 | $0.00066 | $0.00997 |
| Sonnet 5.5 | $0.00033 | $0.00498 |
| Haiku 4.5 | $0.00016 | $0.00249 |
Grade A, and why
stata 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 1mo 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stata Skill — pystata on StataNow 19.5 BE
Run Stata entirely through pystata, the official Python integration that
ships with Stata. Configure the session once, then issue every command — and
run every .do file — with stata.run(). Data crosses between Python and
Stata in memory through pandas, so there is no need to write intermediate
.dta files or read .log files unless the user wants them.
The one rule that matters most
Always execute Stata through pystata. Both individual commands and entire
.do files go through stata.run(...). Never launch StataBE-64.exe as a
subprocess and never run a do-file in batch mode — pystata keeps a single live
Stata session in the Python process, gives direct access to data and stored
results, and raises real Python exceptions on errors. Running a do-file is just
stata.run('do "path/to/file.do"').
Setup
This machine has StataNow 19.5 BE at C:\Program Files\StataNow19, and it
is already on PATH. pystata and stata_setup are installed for the system
Python (3.14). Basic Edition (BE) is the only licensed edition; "se" and
"mp" cannot be initialized.
Configure once per Python process:
import stata_setup
stata_setup.config(r"C:\Program Files\StataNow19", "be")
from pystata import stata
For clean output without the StataCorp splash banner, drive pystata.config
directly instead:
import sys
sys.path.insert(0, r"C:\Program Files\StataNow19\utilities")
import pystata
pystata.config.init("be", splash=False)
from pystata import stata
config.init can run only once per process; to start over, launch a fresh
Python process.
Bundled helper (optional)
scripts/stata_runner.py removes the boilerplate: it bakes in the path and
edition, configures pystata lazily on first use, and wraps command-running,
output capture, and data exchange. Reach for it when a script makes several
Stata calls.
import os
import sys
sys.path.insert(0, os.path.expanduser("~/.claude/skills/stata/scripts"))
import stata_runner as sr
sr.run("sysuse auto, clear")
log = sr.run("regress price mpg weight, robust", capture=True)
print(log)
print("R-squared:", sr.ereturn()["e(r2)"])
What ships with it
4 files 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.
- 1mo ago First seen · 248 lines · 165 tokens per session scan A fd6c63b8d4f6
stata is a skill published in the GitHub repository kennethkhoocy/applied-micro-skills (20 stars, last pushed 1mo ago), licensed MIT. It adds 165 tokens to every session and 2,492 once invoked, about $0.0007 per session on Opus 5.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
literature-searcher
Search CrossRef, OpenAlex, PubMed, Semantic Scholar, and optional Scopus; deduplicate results, download open-access PDFs by DOI, classify papers, monitor new results, and analyze coverage. Use when asked to search literature, monitor a topic, download an open-access paper, classify papers, or analyze literature gaps.
kelly-dog-walk
A dog-walking agent workflow that chooses a daily walking time from a rulebook and checks the decision against real weather data. Changes to the rulebook are submitted for a person to approve rather than applied directly.
ccdb
A lookup tool for Carbonstop's CCDB, a database of carbon-emission factors for activities and materials. It supports checking factors by region and year and comparing their units, boundaries, specifications, and sources.
carbon-data-asset-expert
A specialist workflow for turning carbon-related data into usable carbon assets under MRV rules. MRV means measuring, reporting, and independently checking environmental results.
healthcare-data-compliance-expert
A guide to making healthcare data use lawful, authorised, and clear about ownership. Healthcare data can include sensitive personal information, and human genetic resources may need additional approval.
seed-industry-data-asset-expert
A seed-industry data-asset skill for handling breeding, genetic, weather, soil, farm-machine, and traceability data. It applies rules for seed genetic resources and important agricultural data when turning that information into recognized, investable, or tokenized assets.