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 topprismdata/cultivating-ml-agent --skill feature-engineering-saturation-detectiongit clone --depth 1 https://github.com/topprismdata/cultivating-ml-agentWrote 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/topprismdata/cultivating-ml-agent/feature-engineering-saturation-detection)<a href="https://agentmods.dev/skills/topprismdata/cultivating-ml-agent/feature-engineering-saturation-detection"><img src="https://agentmods.dev/badge/skills/topprismdata/cultivating-ml-agent/feature-engineering-saturation-detection/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/topprismdata/cultivating-ml-agent/feature-engineering-saturation-detection"><img src="https://agentmods.dev/badge/skills/topprismdata/cultivating-ml-agent/feature-engineering-saturation-detection.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.00065 | $0.01794 |
| Opus 5 | $0.00032 | $0.00897 |
| Sonnet 5 | $0.00013 | $0.00359 |
| Haiku 4.5 | $0.00006 | $0.00179 |
Grade A, and why
feature-engineering-saturation-detection 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 10d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Engineering Saturation Detection
Context
Feature engineering always saturates. Every project has a "ceiling" past which new features stop helping. Continuing to optimize past saturation wastes weeks of engineering time. In a recent retail SKU recommendation project, 13 consecutive failed experiments (v31-v43) occurred before recognizing saturation at 76.5% F1 (theoretical ceiling 90.7%). This skill teaches how to detect saturation early and switch paradigms.
The core lesson: optimization without a ceiling is wasted effort. If you don't know your theoretical upper bound, you can't know if you're done.
Guidance
The 4 Saturation Signals
Signal 1: Consecutive F1 Stagnation
- 3-4+ experiments without improvement
- Each new feature adds ≤0.1pp
- Action: Stop adding features, switch paradigm
Signal 2: High Correlation with Existing Features
- New feature has Spearman correlation >0.7 with existing ones
- Captures no new information
- Action: Skip the feature, document why
Signal 3: Distance to Theoretical Upper Bound < 15pp
- F1-EM (oracle ceiling) - actual F1 < 15pp
- Historical coverage ceiling < 10pp above actual
- Action: Optimization ROI is low, consider external data / new paradigm
Signal 4: Improvements Only From Threshold/Window Tuning
- Last 3+ improvements came from "tweak N", "expand window", "adjust threshold"
- No new information captured
- Action: Architectural change needed (model class, data source, real-time signals)
Diagnostic Script
def detect_saturation(experiment_log):
"""Returns saturation status + recommended action"""
recent = experiment_log.tail(5)
# Signal 1: Stagnation (3+ experiments without >0.2pp improvement)
improvements = recent['f1_diff'].tolist()
stagnant = len([x for x in improvements[-3:] if x > 0.002]) == 0
# Signal 3: Distance to ceiling
upper_bound = compute_f1_em_upper_bound() # F1-EM = oracle ceiling
distance_to_ceiling = upper_bound - recent['f1'].iloc[-1]
# Signal 2: Feature correlation
new_feature_max_corr = check_feature_correlation(recent['new_features'])
high_corr = new_feature_max_corr > 0.7
if stagnant and distance_to_ceiling < 0.15:
return "SATURATED — switch paradigm (external data, real-time signals, new model class)"
elif high_corr:
return "FEATURE REDUNDANT — try different angle or skip"
elif distance_to_ceiling < 0.05:
return "NEAR CEILING — declare success and ship"
else:
return "ACTIVE — keep optimizing features"
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.
- 10d ago First seen · 156 lines · 65 tokens per session scan A 77ae038fe2f3
feature-engineering-saturation-detection is a skill published in the GitHub repository topprismdata/cultivating-ml-agent (5 stars, last pushed 12d ago), licensed MIT. It adds 65 tokens to every session and 1,794 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-08-31.
Other skills, from other repositories
huggingface-hub
Hugging Face Hub CLI (hf) — search, download, and upload models and datasets, manage repos, query datasets with SQL, deploy inference endpoints, manage Spaces and buckets.
tensorboard
Visualize training metrics, debug models with histograms, compare experiments, visualize model graphs, and profile performance with TensorBoard - Google's ML visualization toolkit.
mlflow
Track ML experiments, manage model registry with versioning, deploy models to production, and reproduce experiments with MLflow - framework-agnostic ML lifecycle platform.
datachain-knowledge
Use whenever datasets, cloud storage buckets, or data pipelines are mentioned — creating, saving, querying, listing, exploring, deleting, or processing data in S3, GCS, Azure Blob, or local storage. Also use when running any script that may create datasets as a side effect. Maintains a knowledge base at dc-knowledge/…
prompt-scanner
A scanner for text sent to an AI agent, looking for prompt injection and jailbreak attempts. Prompt injection is text that tries to override an agent's instructions; a jailbreak tries to bypass its safety limits.
install-openviking-memory
Install and configure the OpenViking long-term memory plugin for OpenClaw via natural conversation. Once installed, the plugin automatically captures facts from chats and recalls relevant context before each reply (auto-capture + auto-recall, cross-session). Covers prerequisites, install through OpenClaw's plugin…