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 gpu-readiness-assessmentgit 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/gpu-readiness-assessment)<a href="https://agentmods.dev/skills/topprismdata/cultivating-ml-agent/gpu-readiness-assessment"><img src="https://agentmods.dev/badge/skills/topprismdata/cultivating-ml-agent/gpu-readiness-assessment/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/gpu-readiness-assessment"><img src="https://agentmods.dev/badge/skills/topprismdata/cultivating-ml-agent/gpu-readiness-assessment.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.00151 | $0.01643 |
| Opus 5 | $0.00076 | $0.00822 |
| Sonnet 5 | $0.00030 | $0.00329 |
| Haiku 4.5 | $0.00015 | $0.00164 |
Grade A, and why
gpu-readiness-assessment 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 11d 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.
GPU Readiness Assessment
Problem
GPU quota (30h/week) is the scarcest resource in Kaggle. It's shared across ALL competitions. Wrong allocation = wasted hours that block other competitions.
Common mistakes:
- Using GPU for tabular competitions where GBDT on CPU is faster and better
- Running AutoGluon with GPU when CPU preset gives same result in less time
- Starting GPU training before verifying the pipeline works on CPU first
- Spending 8h GPU on feature exploration that could be done in 30 min on CPU
The 5-Gate Assessment
Run all 5 gates in order. Stop at the first FAIL.
Gate 1: Task Type Check
Is the task inherently GPU-friendly?
✅ Image classification/segmentation (CNN, UNet, ViT)
✅ NLP/LLM inference (transformer, BERT, LLaMA)
✅ Large-scale deep learning (>1M parameters)
✅ RL training (neural network policy)
⚠️ Time series with deep learning (LSTM/Transformer — may not beat GBDT)
❌ Tabular classification/regression (GBDT dominates, GPU adds nothing)
❌ Rule-based agent (PTCG, Orbit Wars — pure logic, no ML)
❌ ONNX optimization (NeuroGolf — graph manipulation, no training)
Verdict:
✅ → proceed to Gate 2
❌ → SKIP GPU, use CPU
Gate 2: Data Size Check
Is the dataset large enough to benefit from GPU?
>100K rows × >50 features → GPU helps for NN
>10K images → GPU helps for CNN
<10K rows → CPU is faster (GPU overhead > speedup)
<1K images → CPU + transfer learning is sufficient
Kaggle-specific:
Most Playground series (690K rows) → GBDT on CPU is optimal, GPU NOT needed
Biohub (3D microscopy) → GPU required (UNet inference)
ARC-AGI-3 (LLM agent) → GPU required (27B model inference)
Verdict:
Sufficient data → proceed to Gate 3
Insufficient data → SKIP GPU
Gate 3: Model Architecture Check
Does the best model for this task require GPU?
Neural network (CNN/RNN/Transformer) → GPU required for training
Pre-trained model inference (LLM, UNet) → GPU required for reasonable speed
GBDT (LGB/XGB/CAT) → CPU only (GPU versions exist but rarely better)
Linear/logistic regression → CPU trivially
Rule-based heuristic → CPU trivially
Competition evidence:
House Prices → GBDT CPU (no GPU needed, 0.11750 LB)
s6e7 → GBDT CPU (no GPU needed, 0.94942 LB)
Biohub → UNet GPU (mandatory for 12h inference budget)
PTCG → Rule-based CPU (no ML training)
Verdict:
GPU-native model → proceed to Gate 4
CPU-native model → SKIP GPU
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.
- 11d ago First seen · 156 lines · 151 tokens per session scan A a2317c78ce8e
gpu-readiness-assessment is a skill published in the GitHub repository topprismdata/cultivating-ml-agent (5 stars, last pushed 13d ago), licensed MIT. It adds 151 tokens to every session and 1,643 once invoked, about $0.0008 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…