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-distributednpx skills add NVIDIA/nvalchemi-toolkit --skill nvalchemi-distributedgit 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-distributed)<a href="https://agentmods.dev/skills/nvidia/nvalchemi-toolkit/nvalchemi-distributed"><img src="https://agentmods.dev/badge/skills/nvidia/nvalchemi-toolkit/nvalchemi-distributed.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.00064 | $0.04397 |
| Opus 5 | $0.00032 | $0.02198 |
| Sonnet 5 | $0.00013 | $0.00879 |
| Haiku 4.5 | $0.00006 | $0.00440 |
Grade A, and why
nvalchemi-distributed 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nvalchemi Distributed (Domain Decomposition)
Overview
Domain decomposition (DD) splits one atomic system across several GPUs so a simulation that doesn't fit — or doesn't run fast enough — on a single card can scale out. The same model wrapper, hooks, and integrators you use single-process run unchanged; you add one wrapper around each.
- {class}
~nvalchemi.distributed.DomainParallelwraps any {class}~nvalchemi.dynamics.base.BaseDynamicsintegrator/optimizer and drives it across the mesh. - Under the hood it wraps the model in a
DistributedModel, which reads the model'sdistribution_specto know how to shard/gather each field.
from nvalchemi.distributed import (
DistributedManager, DomainConfig, DomainParallel, HookScope,
)
Launch with torchrun (or SLURM): DD is one process per GPU.
torchrun --nproc_per_node=4 my_distributed_md.py
There are four things you may need to do. Pick the section you need:
- Run a shipped model under DD → §1
- Choose halo vs graph-partition → §2
- Make your own model run under DD (author a
distribution_spec) → §3 - Write a custom integrator that stays correct under DD → §4
1. Run a domain-decomposed model
Bootstrap the process group + mesh with DistributedManager, wrap the model as
usual, then wrap the integrator in DomainParallel. Build the full system on
rank 0, partition() it, and run().
import torch
from nvalchemi.data import AtomicData, Batch
from nvalchemi.distributed import (
DistributedManager, DomainConfig, DomainParallel, HookScope,
)
from nvalchemi.dynamics import NVTLangevin, HostMemory
from nvalchemi.dynamics.hooks import SnapshotHook
from nvalchemi.dynamics.base import DynamicsStage
from nvalchemi.hooks import NeighborListHook
from nvalchemi.models.mace import MACEWrapper
# 1. Bootstrap (reads RANK / WORLD_SIZE / LOCAL_RANK from torchrun).
DistributedManager.initialize()
dm = DistributedManager()
mesh = dm.initialize_mesh(mesh_shape=(dm.world_size,), mesh_dim_names=("domain",))
device = torch.device(dm.device)
# 2. Wrap the model — identical to single-process.
wrapper = MACEWrapper.from_checkpoint("medium-mpa-0", device=device).eval()
# 3. Build the inner integrator (its NeighborListHook is an INNER hook).
integrator = NVTLangevin(
model=wrapper, dt=1.0, temperature=300.0, friction=0.01, n_steps=200,
hooks=[NeighborListHook(wrapper.model_config.neighbor_config, skin=0.5,
stage=DynamicsStage.BEFORE_COMPUTE)],
)
# 4. Trajectory snapshot: gather to rank 0 (an OUTER hook).
snapshot = SnapshotHook(sink=HostMemory(capacity=201), frequency=10)
snapshot.scope = HookScope.RANK_ZERO
# 5. Wrap + run. cutoff = wrapper.cutoff makes the halo width exact.
domain_cfg = DomainConfig(cutoff=float(wrapper.cutoff), skin=0.5, mesh=mesh)
with DomainParallel(dynamics=integrator, config=domain_cfg,
n_steps=200, hooks=[snapshot]) as dynamics:
full_batch = build_full_system(device) if dm.rank == 0 else None
owned = dynamics.partition(full_batch) # returns THIS rank's owned atoms
dynamics.run(owned)
DistributedManager.cleanup()
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 · 362 lines · 64 tokens per session scan A 82bc758f56c2
nvalchemi-distributed is a skill published in the GitHub repository NVIDIA/nvalchemi-toolkit (159 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 4,397 once invoked, about $0.0003 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…