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 Zhang-Henry/CoEvoSkills --skill evo-ecommerce-anomalygit clone --depth 1 https://github.com/Zhang-Henry/CoEvoSkillsWrote 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/zhang-henry/coevoskills/evo-ecommerce-anomaly)<a href="https://agentmods.dev/skills/zhang-henry/coevoskills/evo-ecommerce-anomaly"><img src="https://agentmods.dev/badge/skills/zhang-henry/coevoskills/evo-ecommerce-anomaly/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/zhang-henry/coevoskills/evo-ecommerce-anomaly"><img src="https://agentmods.dev/badge/skills/zhang-henry/coevoskills/evo-ecommerce-anomaly.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.01074 |
| Opus 5 | $0.00026 | $0.00537 |
| Sonnet 5 | $0.00010 | $0.00215 |
| Haiku 4.5 | $0.00005 | $0.00107 |
Grade A, and why
evo-ecommerce-anomaly 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 9d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E-Commerce Anomaly Detection and Causal Analysis
Overview
Generic pipeline for analyzing e-commerce transaction anomalies and their demographic drivers:
- Data cleaning: Removes duplicates, auto-detects and fixes dirty categorical values, fills missing values with mode
- Anomaly detection: Counterfactual forecasting using day-of-week averages with linear trend; anomaly index scaled to [-100, 100]
- Feature engineering: Runtime discovery of ordinal scales, binary indicators, multi-select decomposition, and one-hot encoding
- DiD causal analysis: Univariate DiD for intensive margin (spend) and extensive margin (purchase probability)
End-to-End Usage
The caller supplies file paths and period boundaries from the task instruction.
import sys, os, json
sys.path.insert(0, '/app/environment/skills/evo-ecommerce-anomaly/scripts')
from data_cleaning import clean_survey, clean_purchases
from anomaly_detection import compute_anomaly_index
from feature_engineering import engineer_survey_features
from causal_analysis import run_full_causal_analysis
# --- Caller supplies these from the task instruction ---
survey_path = '<SURVEY_CSV_PATH>' # path to dirty survey CSV
purchase_path = '<PURCHASE_CSV_PATH>' # path to dirty purchase CSV
output_dir = '<OUTPUT_DIR>' # where to write results
treatment_start = '<YYYY-MM-DD>' # start of event/treatment window
treatment_end = '<YYYY-MM-DD>' # end of event/treatment window
baseline_start = '<YYYY-MM-DD>' # start of baseline comparison window
baseline_end = '<YYYY-MM-DD>' # end of baseline comparison window
# -------------------------------------------------------
os.makedirs(output_dir, exist_ok=True)
# Step 1: Clean data
survey_clean = clean_survey(survey_path)
survey_clean.to_csv(f'{output_dir}/survey_cleaned.csv', index=False)
purchases_clean = clean_purchases(purchase_path)
purch_save = purchases_clean.drop(columns=['Total_Spend'], errors='ignore')
date_col = [c for c in purch_save.columns if 'date' in c.lower()][0]
purch_save[date_col] = purch_save[date_col].dt.strftime('%Y-%m-%d')
purch_save.to_csv(f'{output_dir}/purchases_filtered.csv', index=False)
# Step 2: Feature engineering
survey_features = engineer_survey_features(survey_clean)
survey_features.to_csv(f'{output_dir}/survey_feature_engineered.csv', index=False)
# Step 3: Anomaly detection
anomaly_df = compute_anomaly_index(
purchases_clean, treatment_start=treatment_start, treatment_end=treatment_end
)
anomaly_df.to_csv(f'{output_dir}/category_anomaly_index.csv', index=False)
# Step 4: Causal analysis
id_col = survey_features.columns[0]
report, intensive_df, extensive_df = run_full_causal_analysis(
purchases_clean, survey_features, anomaly_df,
baseline_start=baseline_start, baseline_end=baseline_end,
treatment_start=treatment_start, treatment_end=treatment_end,
id_col=id_col
)
intensive_df.to_csv(f'{output_dir}/intensive_margin.csv', index=False)
cat_col = [c for c in extensive_df.columns if 'category' in c.lower()]
cat_col = cat_col[0] if cat_col else 'Category'
extensive_df = extensive_df[[id_col, cat_col, 'Period', 'Has_Purchase']]
extensive_df.to_csv(f'{output_dir}/extensive_margin.csv', index=False)
with open(f'{output_dir}/causal_analysis_report.json', 'w') as f:
json.dump(report, f, indent=2)
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.
- 9d ago First seen · 91 lines · 52 tokens per session scan A 21e1f4d6a52c
evo-ecommerce-anomaly is a skill published in the GitHub repository Zhang-Henry/CoEvoSkills (66 stars, last pushed 23d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,074 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-09-03.
Other skills, from other repositories
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.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
food-order
Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status with ordercli. Use when the user wants to reorder food, check delivery status, or browse recent Foodora order history. Never confirm an order without explicit user approval.
product-description-generator
E-commerce product description generator for any platform. Generates optimized titles, bullet points, descriptions, and backend keywords using competitor research + keyword scoring + FABE copywriting. Two modes: (A) Create — generate listing from product specs with optional competitor analysis, (B) Optimize — improve…
amazon-price-tracker
Amazon price monitoring and competitive pricing intelligence. Real-time price tracking, Buy Box analysis, promotion detection, and dynamic pricing strategy optimization. Use when the user asks about price monitoring, competitor pricing, Buy Box tracking, or pricing strategy.