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 SFETNI/Deep-Matter-Chem-Skills --skill md-force-fieldsgit clone --depth 1 https://github.com/SFETNI/Deep-Matter-Chem-SkillsWrote 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/sfetni/deep-matter-chem-skills/md-force-fields)<a href="https://agentmods.dev/skills/sfetni/deep-matter-chem-skills/md-force-fields"><img src="https://agentmods.dev/badge/skills/sfetni/deep-matter-chem-skills/md-force-fields/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/sfetni/deep-matter-chem-skills/md-force-fields"><img src="https://agentmods.dev/badge/skills/sfetni/deep-matter-chem-skills/md-force-fields.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.00003 | $0.19142 |
| Opus 5 | $0.00002 | $0.09571 |
| Sonnet 5 | $0.00001 | $0.03828 |
| Haiku 4.5 | $0.00000 | $0.01914 |
Grade A, and why
md-force-fields 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 — 1,176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MD Force Fields
Description
This skill covers selection, validation, and deployment of interatomic force fields for molecular dynamics: the physical basis and transferability limits of every major functional form (EAM, MEAM, Tersoff, Stillinger-Weber, Buckingham, COMB, ReaxFF, AMBER, CHARMM, OPLS, GROMOS, and ML potentials); parameter-file sourcing and provenance verification; unit and format compatibility across LAMMPS, GROMACS, OpenMM, and ASE; mixing rules, long-range electrostatics, cutoff conventions, neighbor-list settings, and bonded constraints; and validation of any force field against DFT, experiment, or higher-level simulation. Invoke this skill when selecting a force field for a new system, diagnosing a simulation failure that may originate from a wrong or misapplied force field, or verifying the transferability of an existing parameterization to a new application domain.
Domain Context
A force field is a function that maps a set of atomic positions {rᵢ} to a potential energy U({rᵢ}) and, by differentiation, to forces Fᵢ = -∂U/∂rᵢ. Every force field encodes assumptions about which physical interactions are important and which are negligible. These assumptions are baked into the functional form; they cannot be corrected by changing parameter values alone.
The central issue with force fields is transferability: a parameterization fitted to reproduce a set of reference properties in one regime is not guaranteed to be accurate in a different regime. The reference data (crystal structures, elastic constants, bond lengths, heats of formation, vibrational frequencies) used to fit the parameters determines the validity domain. Using the force field outside that domain is extrapolation — the errors are unbounded and often silent.
Hierarchy of approximations, from most to least severe:
- Born-Oppenheimer surface: All classical force fields assume the ground-state PES. Electronically excited states, non-adiabatic dynamics, metallic-band effects on bonding, and charge-transfer-driven structural changes are outside the Born-Oppenheimer classical picture entirely.
- Fixed topology vs. reactive: Fixed-topology force fields (AMBER, CHARMM, EAM, Tersoff) assign bonds at the start of the simulation and never break or form them. Reactive force fields (ReaxFF, COMB) allow bond-order to vary continuously. ML potentials can be either reactive or non-reactive depending on the training data.
- Many-body vs. pairwise: Pure pairwise potentials (LJ, Buckingham) cannot reproduce the Cauchy pressure discrepancy in metals (C₁₂ ≠ C₄₄) or the angular dependence of covalent bonds. Many-body terms (EAM embedding energy, Tersoff bond-order, AMBER dihedral) correct specific deficiencies but add parameters.
- Classical nuclei: All MD force fields integrate classical equations of motion. Zero-point energy and nuclear tunneling are neglected. This fails for light atoms (H, He, Li) at low temperature.
- Mean-field charges: Classical force fields use fixed partial charges (AMBER, CHARMM) or fluctuating charges (ReaxFF QEq, COMB). Neither is a first-principles electron density; both fail when charge delocalization or metallic screening becomes important.
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 · 1,176 lines · 3 tokens per session scan A cf9be97b5a20
md-force-fields is a skill published in the GitHub repository SFETNI/Deep-Matter-Chem-Skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 3 tokens to every session and 19,142 once invoked, about $0.0000 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
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…
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.
patsnap-biological-modality
Biological sequence and modality intelligence via Patsnap MCP.
patsnap-scientific-translational-evidence
Patsnap Scientific & Translational Evidence MCP for AI agents. Retrieval platform focusing on scientific literature and translational outcomes, covering academic publication queries and translational medicine record tracking.
patsnap-solution-engine
Patsnap TRIZ Concept Solution Engine MCP for AI agents. Generates innovation or product cost-reduction concepts through asynchronous TRIZ and TRIZ/DFMA workflows. Use for engineering problem solving, concept alternatives, cost-reduction analysis, task-progress retrieval, and selected-solution details.
patsnap-current-awareness
Patsnap Current Awareness MCP for AI agents. Tracking system for pharmaceutical industry dynamics and cutting-edge news, covering global medical news search and in-depth news detail mining.