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/gemini-cli-extensions/data-agent-kit-starter-pack/ml-best-practicesnpx skills add gemini-cli-extensions/data-agent-kit-starter-pack --skill ml-best-practicesgit clone --depth 1 https://github.com/gemini-cli-extensions/data-agent-kit-starter-packWrote 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/gemini-cli-extensions/data-agent-kit-starter-pack/ml-best-practices)<a href="https://agentmods.dev/skills/gemini-cli-extensions/data-agent-kit-starter-pack/ml-best-practices"><img src="https://agentmods.dev/badge/skills/gemini-cli-extensions/data-agent-kit-starter-pack/ml-best-practices.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.00129 | $0.02023 |
| Opus 5 | $0.00064 | $0.01012 |
| Sonnet 5 | $0.00026 | $0.00405 |
| Haiku 4.5 | $0.00013 | $0.00202 |
Grade A, and why
ml-best-practices 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- ml-best-practices — 100% identical, 0 lines differ
- ml-best-practices — 100% identical, 0 lines differ
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 Best Practices
I want to read a story about the data, not just run code. Ensure every code cell is followed by a markdown cell analyzing the results. End the notebook with a summary comprehensively answering the prompt.
If there is a good match between the user's request and a corresponding example plan, then adapt the example plan to fully answer the user's request:
Clustering:
Identify distinct groups based on their features.
- Understand the schema and field descriptions.
- Visualize features referenced in the prompt (e.g., with histograms, scatterplots).
- Transform dates into timestamps.
- Before applying encoders, check if the dataset already contains pre-encoded features and prefer existing numerical representations.
- Prefer to keep data instead of dropping it when possible.
- Transform ordinal data with an ordinal encoder.
- Transform nominal data with a one hot encoder.
- Standardize numerical features.
- Perform clustering with a range of values, and collect the silhouette score.
- Choose the optimal number of clusters based on the silhouette score.
- Use dimensionality reduction (e.g., PCA) to project the data into two dimensions.
- Scatterplot the samples in two dimensions with cluster labels as the hue.
- Scatterplot the samples in two dimensions with a discrete feature as the hue.
- Describe the clusters in text by feature distributions or typical feature values.
- Conclusion: comprehensively answer the prompt in a final markdown cell.
Time Series Forecasting:
Develop a predictive model to estimate future values based on historical trends. How might different modeling approaches impact the prediction accuracy?
- Understand the schema and field descriptions.
- Visualize the target feature over time at a reasonable granularity.
- Always perform a chronological split on the data to create training, validation, and test sets.
- Are there seasonal trends?
- Test for stationarity.
- Discuss possible modeling approaches. How might different modeling approaches impact the prediction accuracy?
- Train two time series forecasting models to predict the target feature. Use previous seasonality and stationarity information as model hyperparameters.
- Predict the target feature for the training and validation sets.
- Optionally, hypertune models with the validation set.
- Visualize the actual and predicted target feature vs time for each model on the training and validation sets.
- Evaluate the validation performance with error metrics.
- Select a model.
- Retrain the selected model on the test and validation sets.
- Predict the test values with the selected model.
- Visualize the average target feature and the predicted test values.
- Conclusion: comprehensively answer the prompt in a final markdown cell.
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 · 129 tokens per session scan A ae010fd52e6b
ml-best-practices is a skill published in the GitHub repository gemini-cli-extensions/data-agent-kit-starter-pack (179 stars, last pushed today), licensed Apache-2.0. It adds 129 tokens to every session and 2,023 once invoked, about $0.0006 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.