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 wentorai/research-plugins --skill modeling-strategy-guidegit clone --depth 1 https://github.com/wentorai/research-pluginsWrote 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/wentorai/research-plugins/modeling-strategy-guide)<a href="https://agentmods.dev/skills/wentorai/research-plugins/modeling-strategy-guide"><img src="https://agentmods.dev/badge/skills/wentorai/research-plugins/modeling-strategy-guide.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.00016 | $0.01983 |
| Opus 5 | $0.00008 | $0.00992 |
| Sonnet 5 | $0.00003 | $0.00397 |
| Haiku 4.5 | $0.00002 | $0.00198 |
Grade A, and why
modeling-strategy-guide 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 7d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modeling Strategy Guide
A skill for strategic statistical modeling applied to academic research. Covers advanced modeling decisions, experimental design, causal inference, feature engineering, and the critical thinking required to move from data to defensible conclusions.
Overview
Senior data scientists distinguish themselves not by knowing more algorithms but by asking better questions, designing cleaner experiments, and being honest about what the data can and cannot tell them. This skill translates that professional discipline into a research context, helping academics apply modern data science practices to their empirical work. It covers the strategic decisions that matter most: when to use simple models versus complex ones, how to establish causality rather than mere correlation, and how to communicate uncertainty honestly.
The skill is particularly useful for researchers working with observational data who need causal inference techniques, those designing randomized experiments who need proper power calculations and analysis plans, and anyone building predictive models who needs to avoid common overfitting and leakage pitfalls.
Strategic Modeling Decisions
Model Selection Philosophy
Decision Framework:
1. Start with the simplest model that could answer your question
2. Add complexity only when diagnostics reveal inadequacy
3. Prefer interpretable models unless prediction accuracy is the sole goal
4. Always have a baseline (mean, majority class, last observation)
Model Complexity Ladder:
Level 1: Descriptive statistics, cross-tabulations
Level 2: Linear/logistic regression
Level 3: Regularized regression (Lasso, Ridge, Elastic Net)
Level 4: Tree ensembles (Random Forest, Gradient Boosting)
Level 5: Deep learning (only with sufficient data and clear justification)
Feature Engineering Principles
import pandas as pd
import numpy as np
def engineer_features(df: pd.DataFrame, config: dict) -> pd.DataFrame:
"""
Apply systematic feature engineering based on domain knowledge.
config example:
{
'log_transform': ['income', 'citations'],
'interactions': [('experience', 'education')],
'polynomial': {'age': 2},
'time_features': 'date_column',
'lag_features': {'metric': [1, 7, 30]}
}
"""
df = df.copy()
# Log transforms for right-skewed variables
for col in config.get('log_transform', []):
df[f'{col}_log'] = np.log1p(df[col])
# Interaction terms
for col_a, col_b in config.get('interactions', []):
df[f'{col_a}_x_{col_b}'] = df[col_a] * df[col_b]
# Polynomial features
for col, degree in config.get('polynomial', {}).items():
for d in range(2, degree + 1):
df[f'{col}_pow{d}'] = df[col] ** d
# Time-based features
if 'time_features' in config:
time_col = config['time_features']
df[time_col] = pd.to_datetime(df[time_col])
df[f'{time_col}_month'] = df[time_col].dt.month
df[f'{time_col}_dayofweek'] = df[time_col].dt.dayofweek
df[f'{time_col}_quarter'] = df[time_col].dt.quarter
return df
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.
- 7d ago First seen · 224 lines · 16 tokens per session scan A b48973ec2ff7
modeling-strategy-guide is a skill published in the GitHub repository wentorai/research-plugins (288 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 1,983 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-30.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…