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/learningmatter-mit/atomisticskills/ml-property-predictornpx skills add learningmatter-mit/AtomisticSkills --skill ml-property-predictorgit clone --depth 1 https://github.com/learningmatter-mit/AtomisticSkillsWrote 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/learningmatter-mit/atomisticskills/ml-property-predictor)<a href="https://agentmods.dev/skills/learningmatter-mit/atomisticskills/ml-property-predictor"><img src="https://agentmods.dev/badge/skills/learningmatter-mit/atomisticskills/ml-property-predictor.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.00045 | $0.01180 |
| Opus 5 | $0.00023 | $0.00590 |
| Sonnet 5 | $0.00009 | $0.00236 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
ml-property-predictor 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 yesterday.
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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MLIP Property Predictor Training
Goal
To leverage pre-trained GNN representations from MLIPs to train an independent readout head for any custom scalar target property (e.g., bulk modulus, bandgap, formation energy, or spin states) directly from crystal or molecular structures.
Overview
This skill allows you to leverage pre-trained GNN representations from MLIPs to train an independent readout head for any custom scalar target property, such as bulk modulus, bandgap, formation energy, or spin states.
To keep the core MLIP wrappers clean, property prediction in AtomisticSkills is handled by standalone training scripts located in the .agents/skills/ml-property-predictor/scripts/ directory.
Workflow
- Prepare Data: Build a
.jsonor.xyzdataset containing structures and the corresponding scalar property labels. JSON datasets should be lists of dicts containing astructurekey (Pymatgen format) and your target property key. - Determine Property Type: Determine if the property is
"intensive"(e.g. Bandgap, Bulk Modulus) or"extensive"(e.g. Total Energy).- MatGL logic: For intensive targets, node features undergo a global graph readout (like
Set2Set) before passing through an MLP. For extensive targets, the MLP outputs atomic properties which are then sum-pooled. - MACE logic: MACE natively supports extensive targets by predicting site-wise scalar outputs and sum-pooling them. When intensive properties are targeted, MACE still sum-pools site-wise outputs, forcing the model to internally learn the intensive invariant.
- MatGL logic: For intensive targets, node features undergo a global graph readout (like
- Execute Script: Run the MACE or MatGL property prediction script in their respective Conda environments.
Example 1: Training a MACE Property Predictor
MACE property training is handled by scripts/train_mace_property.py. It dynamically patches the mace.cli.run_train module to freeze the backbone (if requested) and inject a custom intensive/extensive property readout.
# Env: mace-agent
# Run the standalone MACE property training script
python .agents/skills/ml-property-predictor/scripts/train_mace_property.py \
--data_path .agents/test/mp_bulk_modulus.json \
--model_name MACE-OMAT-0-small \
--target_property bulk_modulus \
--property_type intensive \
--epochs 30 \
--batch_size 16 \
--lr 0.001 \
--output_dir custom_mace_results/
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/mace_bulk_modulus/README.md 1.5 KB
- examples/mace_bulk_modulus/run_mace.py 2.6 KB runs code
- examples/matgl_bulk_modulus/matgl_model/model.json 2.4 KB
- examples/matgl_bulk_modulus/matgl_model/model.pt 2.5 KB
- examples/matgl_bulk_modulus/matgl_model/state.pt 1166 KB
- examples/matgl_bulk_modulus/README.md 1.5 KB
- examples/matgl_bulk_modulus/run_matgl.py 2.5 KB runs code
- scripts/train_mace_property.py 8.0 KB runs code
- scripts/train_matgl_property.py 11 KB runs code
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.
- yesterday First seen · 93 lines · 45 tokens per session scan A 13f66ad00991
ml-property-predictor is a skill published in the GitHub repository learningmatter-mit/AtomisticSkills (158 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,180 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
hugging-face-trackio
Track and visualize ML training experiments with Trackio. Use when logging metrics during training (Python API) or retrieving/analyzing logged metrics (CLI). Supports real-time dashboard visualization, HF Space syncing, and JSON output for automation.
pysr
Use when fitting equations to data with PySR or SymbolicRegression.jl, when a user wants an interpretable formula, symbolic model, scaling law, or empirical relation discovered from numeric data, or when debugging a PySR search that is slow, stuck, or giving poor equations.
datamol
Pythonic wrapper around RDKit with simplified interface and sensible defaults. Preferred for standard drug discovery including SMILES parsing, standardization, descriptors, fingerprints, clustering, 3D conformers, parallel processing. Returns native rdkit.Chem.Mol objects. For advanced control or custom parameters…
drug-design
End-to-end drug discovery pipeline orchestration. Deterministic Python script that auto-chains structure prediction, pocket detection, de novo design, docking, scoring, and ADMET filtering into reproducible workflows.
molecular-optimization
Iterative lead optimization with analyze-reason-generate-verify-evaluate loop. Paper-backed (MT-Mol, DrugR, MultiMol).
admet_genetic
ADMET-guided genetic molecule optimization workflow from seed SMILES; use when the agent needs to build or run an RDKit/SA-Score/ADMET-AI GA pipeline for molecule optimization, enforce molecule lineage logs, render optimization-history HTML dashboards, and write candidate triage reports.