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/nvidia/nvalchemi-toolkit/nvalchemi-training-apinpx skills add NVIDIA/nvalchemi-toolkit --skill nvalchemi-training-apigit clone --depth 1 https://github.com/NVIDIA/nvalchemi-toolkitWrote 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/nvidia/nvalchemi-toolkit/nvalchemi-training-api)<a href="https://agentmods.dev/skills/nvidia/nvalchemi-toolkit/nvalchemi-training-api"><img src="https://agentmods.dev/badge/skills/nvidia/nvalchemi-toolkit/nvalchemi-training-api.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 | $0.00117 | $0.02422 |
| Opus 5 | $0.00059 | $0.01211 |
| Sonnet 5 | $0.00023 | $0.00484 |
| Haiku 4.5 | $0.00012 | $0.00242 |
Grade A, and why
nvalchemi-training-api 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 4d 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nvalchemi Training API
Overview
Use TrainingStrategy as the owner of one training job: model(s), dataloaders,
loss, optimizer/scheduler config, validation, hooks, runtime counters, and
checkpoints. For full details, see docs/userguide/training.md,
docs/userguide/losses.md, and docs/modules/training/checkpoints.rst.
import torch
from nvalchemi.data import Batch
from nvalchemi.models.base import BaseModelMixin
from nvalchemi.training import (
CheckpointHook,
ComposedLossFunction,
CosineWeight,
EnergyMSELoss,
ForceMSELoss,
LinearWeight,
OptimizerConfig,
StressMSELoss,
TrainingStrategy,
ValidationConfig,
create_model_spec,
)
Minimal Pattern
loss_fn = ComposedLossFunction(
[EnergyMSELoss(), ForceMSELoss()],
weights=[1.0, 10.0],
normalize_weights=False,
)
strategy = TrainingStrategy(
models=model,
optimizer_configs=OptimizerConfig(
optimizer_cls=torch.optim.AdamW,
optimizer_kwargs={"lr": 1e-4, "weight_decay": 1e-5},
),
loss_fn=loss_fn,
validation_config=ValidationConfig(validation_data=val_loader, every_n_epochs=1),
hooks=[CheckpointHook("runs/example/checkpoints", epoch_interval=1)],
num_epochs=20,
)
strategy.run(train_loader)
Model-Agnostic Inputs
Accept any torch.nn.Module that works with the selected training_fn. Prefer
wrapped BaseModelMixin models for standard AtomicData/Batch contracts;
see the nvalchemi-model-wrapping skill or docs/userguide/models.md when
adapting arbitrary MLIPs.
Make model construction reproducible when possible. Use native checkpoint
constructors that carry a spec, or store a create_model_spec(...) for custom
wrappers so strategy checkpoints can rebuild the model before loading weights.
Treat foreign checkpoints as imported weights until a fresh TrainingStrategy
checkpoint has been saved.
Custom Training Functions
Use training_fn when the batch needs custom routing, multiple models, teacher
outputs, auxiliary predictions, or non-standard model outputs. It receives
(model, batch) for a single model or (models, batch) for named models and
returns the prediction mapping consumed by loss_fn.
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.
- 4d ago First seen · 282 lines · 117 tokens per session scan A 902128f59ca5
nvalchemi-training-api is a skill published in the GitHub repository NVIDIA/nvalchemi-toolkit (159 stars, last pushed today), licensed Apache-2.0. It adds 117 tokens to every session and 2,422 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…