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 agentmods add skills/wentorai/research-plugins/ml-experiment-trackernpx skills add wentorai/research-plugins --skill ml-experiment-trackergit 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/ml-experiment-tracker)<a href="https://agentmods.dev/skills/wentorai/research-plugins/ml-experiment-tracker"><img src="https://agentmods.dev/badge/skills/wentorai/research-plugins/ml-experiment-tracker.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.00017 | $0.01807 |
| Opus 5 | $0.00009 | $0.00903 |
| Sonnet 5 | $0.00003 | $0.00361 |
| Haiku 4.5 | $0.00002 | $0.00181 |
Grade A, and why
ml-experiment-tracker 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 6d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ML Experiment Tracker
A skill for planning, executing, and tracking machine learning experiments with full reproducibility. Covers experiment design, hyperparameter management, metric logging, model versioning, and comparison across runs to support rigorous ML research.
Overview
Machine learning research involves running dozens or hundreds of experiments with varying architectures, hyperparameters, data splits, and preprocessing pipelines. Without systematic tracking, it becomes impossible to reproduce results, compare configurations, or identify which changes actually improved performance. This skill provides a structured methodology for experiment management that aligns with academic standards for reproducible ML research.
The approach is framework-agnostic but demonstrates integration with MLflow, Weights & Biases, and plain file-based logging. It emphasizes the practices needed for publications: complete hyperparameter documentation, statistical significance testing across runs, and artifact management for model checkpoints and evaluation outputs.
Experiment Design Framework
Defining an Experiment Plan
Before writing any training code, document the experiment plan:
# experiment_plan.yaml
experiment:
name: "transformer-sentiment-analysis-v3"
hypothesis: "Adding relative positional encoding improves F1 on long reviews (>512 tokens)"
dataset:
name: "imdb-extended"
version: "2025.1"
splits: {train: 0.8, val: 0.1, test: 0.1}
stratify_by: "label"
random_seed: 42
baselines:
- name: "bert-base-uncased"
checkpoint: "bert-base-uncased"
- name: "roberta-base"
checkpoint: "roberta-base"
variables:
independent:
- positional_encoding: ["absolute", "relative", "rotary"]
controlled:
- learning_rate: 2e-5
- batch_size: 32
- max_epochs: 10
- early_stopping_patience: 3
- optimizer: "AdamW"
- weight_decay: 0.01
metrics:
primary: "f1_macro"
secondary: ["accuracy", "precision_macro", "recall_macro", "loss"]
report_at: ["best_val", "final"]
compute:
gpus: 1
estimated_time_per_run: "45min"
total_runs: 9 # 3 encodings x 3 seeds
seeds: [42, 123, 456]
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.
- 6d ago First seen · 213 lines · 17 tokens per session scan A 5312c09cdae1
ml-experiment-tracker is a skill published in the GitHub repository wentorai/research-plugins (287 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 1,807 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
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.