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 OpenLAIR/OpenSkill --skill evo-trend-anomaly-causal-inferencegit clone --depth 1 https://github.com/OpenLAIR/OpenSkillWrote 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/openlair/openskill/evo-trend-anomaly-causal-inference)<a href="https://agentmods.dev/skills/openlair/openskill/evo-trend-anomaly-causal-inference"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-trend-anomaly-causal-inference/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/openlair/openskill/evo-trend-anomaly-causal-inference"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-trend-anomaly-causal-inference.svg" alt="Reviewed on agentmods" width="80" 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.00047 | $0.00731 |
| Opus 5 | $0.00023 | $0.00365 |
| Sonnet 5 | $0.00009 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
evo-trend-anomaly-causal-inference scanned grade A with 1 finding 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 yesterday.
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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
subprocess.run(['python3', '/app/environment/skills/evo-trend-anomaly-causal-inference/scripts/clean_data.py'], check=True) How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evo Trend Anomaly Causal Inference
Complete pipeline for identifying anomalous product category spending patterns and using DiD causal inference to explain anomalies through demographic factors.
Pipeline Steps
- Data Cleaning (
scripts/clean_data.py): Clean survey and purchase data, handling duplicates, missing values, inconsistent formatting, date parsing, monetary columns, and category extraction. - Anomaly Detection (
scripts/anomaly_detection.py): Prophet-based counterfactual forecasting to compute deviation index (-100 to 100) per category for March 2020. - Feature Engineering (
scripts/feature_engineering.py): One-hot/ordinal encode demographics, bin continuous variables, produce feature-engineered survey CSV. - DiD Analysis (
scripts/did_analysis.py): Difference-in-Differences causal analysis for intensive margin (univariate DiD on spend among purchasers) and extensive margin (multivariate heterogeneous DiD on purchase propensity).
Usage
import subprocess
subprocess.run(['python3', '/app/environment/skills/evo-trend-anomaly-causal-inference/scripts/clean_data.py'], check=True)
subprocess.run(['python3', '/app/environment/skills/evo-trend-anomaly-causal-inference/scripts/anomaly_detection.py'], check=True)
subprocess.run(['python3', '/app/environment/skills/evo-trend-anomaly-causal-inference/scripts/feature_engineering.py'], check=True)
subprocess.run(['python3', '/app/environment/skills/evo-trend-anomaly-causal-inference/scripts/did_analysis.py'], check=True)
Key Design Decisions
- Survey IDs are case-sensitive (R_ prefix preserved)
- hh-size outliers (53, 33, etc.) capped using IQR method
- Prophet trained on all pre-March 2020 data only; cmdstanpy logging suppressed
- Anomaly index: 100 * tanh(raw_deviation) for [-100, 100] range
- Binary variable one-hot: remove negative indicator (e.g., _No, _Female) to avoid dummy variable trap
- Intensive margin: purchasers only (Total_Spend > 0), sum spending per user-category-period
- Extensive margin: full cross-join of all survey users × selected categories × periods
- Univariate DiD for intensive margin (robust to small samples), multivariate heterogeneous DiD for extensive margin
- Surge drivers sorted descending, slump drivers sorted ascending by DiD estimate
- JSON serialization uses custom NpEncoder to handle numpy types
- Robust error handling: skips categories with insufficient data, handles singular matrices, validates variance before regression
What ships with it
3 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.
- yesterday First seen · 49 lines · 47 tokens per session scan A 3b9d3aac068c
evo-trend-anomaly-causal-inference is a skill published in the GitHub repository OpenLAIR/OpenSkill (90 stars, last pushed 2d ago), licensed Apache-2.0. It adds 47 tokens to every session and 731 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-11.
Other skills, from other repositories
stripe-best-practices
Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax…
Cursor rules for Medusa
Skill "Cursor rules for Medusa" from AmariahAK/atlarix-skills, covering cursor rules for medusa, when to use this skill, source, medusa rules and general rules.
Medusa rules and best practices
Medusa rules and best practices. These rules should be used when building applications with Medusa.
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
experimental-design
Best practices for designing reproducible ML experiments. Use when planning ablations, baselines, or controlled experiments.