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 instructions/nvidia/nvalchemi-toolkit/agents-mdgit clone --depth 1 https://github.com/NVIDIA/nvalchemi-toolkitWhat 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.02740 | $0.02740 |
| Opus 5 | $0.01370 | $0.01370 |
| Sonnet 5 | $0.00548 | $0.00548 |
| Haiku 4.5 | $0.00274 | $0.00274 |
Grade A, and why
nvalchemi-toolkit AGENTS.md 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 2d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - NVIDIA ALCHEMI Toolkit
Guidelines for AI coding agents operating in this repository.
Project Overview
nvalchemi-toolkit provides the nvalchemi Python package: a GPU-first
framework for AI atomic simulation workflows. It covers graph-structured atomic
data, model wrappers for machine-learned interatomic potentials, batched
dynamics, hooks/reporting, and training/finetuning workflows.
- Python support:
>=3.11,<3.14; CI and setup examples use Python 3.12. - Package manager:
uv; build backend:hatchling. - Core dependencies: PyTorch, Pydantic v2, jaxtyping, TensorDict, Zarr, Rich,
PhysicsNeMo, and
nvalchemi-toolkit-ops. - The project is in public beta. Public PRs may not be accepted immediately, but bug reports, feature requests, and scoped implementation discussions are welcome.
Repository Practices
- Commits need DCO sign-off and Conventional Commits-style messages:
git commit -s -m "fix: describe change". Pre-commit hooks are required; PRs that skip them are not expected to be reviewed. SeeCONTRIBUTING.mdfor DCO details, hook setup, and CI stages. - The PR template expects a short description, testing notes, changelog updates, docstring/docs updates where applicable, and the relevant type-of-change box.
- Keep work tightly scoped; read
docs/userguide/about/before broad changes.
CUDA And Environment Setup
First check CUDA availability:
nvidia-smi
- If
nvidia-smiis missing or reports no usable device, use defaultuvcommands without CUDA extras where possible. - If it reports CUDA 12.x, pass
--extra cu12touvcommands andCUDA_EXTRA=cu12tomaketargets. - If it reports CUDA 13.x,
cu13is the default Makefile extra; explicit commands can still use--extra cu13orCUDA_EXTRA=cu13. - Do not use
uv sync --all-extras: the CUDA variants and some model extras are mutually exclusive.
Common setup commands:
# Default development environment; Makefile currently defaults CUDA_EXTRA=cu13.
make install
# CUDA 12 development environment.
make install CUDA_EXTRA=cu12
# Add CUDA-aligned optional extras, for example MACE.
make install CUDA_EXTRA=cu12 OPTIONAL_EXTRAS=mace
# Direct uv equivalents.
uv sync --extra cu13
uv sync --extra cu12 --extra mace
# Include documentation dependencies when needed.
uv sync --extra cu13 --group docs
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.
- 2d ago First seen · 233 lines · 2,740 tokens per session scan A 66db104387be
nvalchemi-toolkit AGENTS.md is an instructions file published in the GitHub repository NVIDIA/nvalchemi-toolkit (150 stars, last pushed 8d ago), licensed Apache-2.0. It adds 2,740 tokens to every session, about $0.0137 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 instructions, from other repositories
OpenBioMed CLAUDE.md
Instructions for PharMolix/OpenBioMed, covering claude.md, project overview, key commands, environment setup and training.
viral-ngs copilot-instructions.md
Instructions for broadinstitute/viral-ngs, covering copilot instructions, quick reference, running tests and key files.
pysm AGENTS.md
Instructions for galsci/pysm, covering repository guidelines, project overview, project structure & key files, quick start commands and setup environment.
sciplot-academic copilot-instructions.md
Instructions for rippleshe/sciplot-academic, covering sciplot academic - github copilot 使用指南, 🚨 默认触发规则(最高优先级), 🔥 触发关键词(出现任何一个立即触发), 🔥 触发场景(满足任一立即触发) and 🔥 隐含触发(95% 触发).
PyAutoArray AGENTS.md
Instructions for PyAutoLabs/PyAutoArray, covering pyautoarray — agent instructions, what this repo is, related repos, architecture and quick commands.
FaST-LMM AGENTS.md
Instructions for fastlmm/FaST-LMM, covering coding notes for agents, general policies, cross-repository release coordination, numerical correctness and error handling.