Borrowing it
Nothing to install: this file belongs to DuqueOM/ML-MLOps-Portfolio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DuqueOM/ML-MLOps-Portfolio/main/.devin/skills/concept-drift-analysis/SKILL.mdgit clone --depth 1 https://github.com/DuqueOM/ML-MLOps-PortfolioWrote 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/duqueom/ml-mlops-portfolio/concept-drift-analysis)<a href="https://agentmods.dev/skills/duqueom/ml-mlops-portfolio/concept-drift-analysis"><img src="https://agentmods.dev/badge/skills/duqueom/ml-mlops-portfolio/concept-drift-analysis.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.00018 | $0.01584 |
| Opus 5 | $0.00009 | $0.00792 |
| Sonnet 5 | $0.00004 | $0.00317 |
| Haiku 4.5 | $0.00002 | $0.00158 |
Grade A, and why
concept-drift-analysis 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 8d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Concept Drift Analysis
This skill is the RCA counterpart to drift-detection. Where PSI detects
feature-distribution change, this skill detects and diagnoses
performance degradation using delayed ground-truth labels.
Inputs you need
reports/performance.jsonfrom the most recent CronJob run (or manual run)- Baseline metrics from training:
models/baseline_metrics.json - (Optional)
drift_report.jsonto cross-reference with PSI
Decision tree
Performance alert fired
│
┌─────────────┴─────────────┐
Global AUC low? Only sliced AUC low?
│ │
┌───────┴───────┐ ┌─────────┴─────────┐
Data drift No drift Drift in same slice? No drift?
│ │ │ │
Retrain on Label noise Targeted retrain Label quality
fresh data or real or feature fix in that segment
concept drift
Step 1: Read the report
jq '.status, .global, .alerts' reports/performance.json
jq '.slices' reports/performance.json # per-slice breakdown
Identify which slices fired alerts. Each entry has:
{ "slice_name": "by_country", "slice": "country=ES", "metric": "auc",
"value": 0.58, "threshold": 0.65 }
Step 2: Distinguish global vs sliced
# Global AUC
jq '.global.auc' reports/performance.json
# All slice AUCs, sorted ascending
jq -r '.slices | to_entries[] | .value | to_entries[] | [.key, .value.auc] | @tsv' \
reports/performance.json | sort -k2 -n
- Global degradation (many slices low) → population-wide concept drift
- Single-slice degradation (others healthy) → subpopulation issue
- Healthy global, healthy slices → false alarm from window size
Step 3: Cross-reference with data drift
Correlate slice degradation with feature PSI in the SAME window:
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.
- 8d ago First seen · 172 lines · 18 tokens per session scan A 8697892448ee
concept-drift-analysis is a skill published in the GitHub repository DuqueOM/ML-MLOps-Portfolio (5 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 1,584 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-31.
Other skills, from other repositories
mlflow
Track ML experiments, manage model registry with versioning, deploy models to production, and reproduce experiments with MLflow - framework-agnostic ML lifecycle platform.
setup
Configure MLflow tracing for Claude Code.
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.
ml-expert
Expert-level machine learning, deep learning, model training, and MLOps. Use when the user mentions machine learning, deep learning, neural networks, MLOps, or data science, or when the task involves Machine Learning Fundamentals, Data Preparation, or Model Training.
ecs-genai
Use whenever someone runs a GPU / ML / GenAI / LLM workload on Amazon ECS: GPU on ECS, ECS GPU-optimized AMI, g4dn/g5/g6/p4/p5 on ECS, which ECS launch type for GPU, Inferentia/Trainium/Neuron on ECS, distributed training, model inference or vLLM/Triton/TGI/Ray on ECS, Capacity Blocks, GPU sharing, ASG per GPU type.…
eks-genai
Use whenever someone is building, training, fine-tuning, or serving a generative AI / LLM workload on Amazon EKS — phrased as "GPU vs Trainium/Inferentia", "vLLM on EKS", "Ray Serve / KubeRay", "distributed training on EKS", "FSx for Lustre for ML", "Karpenter for GPU", "EFA / NCCL multi-node", "DCGM / Neuron…