PhysicsNeMo is an open-source PyTorch framework for creating, training, and fine-tuning machine-learning models for physics, scientific computing, and engineering. Researchers and engineers use its reusable components and training recipes for applications such as aerodynamics, weather forecasting, structural mechanics, geophysics, and thermal design. The catalogue entries provide rules and skills for working with PhysicsNeMo projects.
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 rules/nvidia/physicsnemo/mod-007b-cannot-remove-or-rename-parameters-without-compat-mappergit clone --depth 1 https://github.com/NVIDIA/physicsnemoWrote 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/rules/nvidia/physicsnemo/mod-007b-cannot-remove-or-rename-parameters-without-compat-mapper)<a href="https://agentmods.dev/rules/nvidia/physicsnemo/mod-007b-cannot-remove-or-rename-parameters-without-compat-mapper"><img src="https://agentmods.dev/badge/rules/nvidia/physicsnemo/mod-007b-cannot-remove-or-rename-parameters-without-compat-mapper.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.1 | $0.00029 | $0.00713 |
| Opus 5 | $0.00015 | $0.00357 |
| Sonnet 5 | $0.00006 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
mod-007b-cannot-remove-or-rename-parameters-without-compat-mapper 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 6d 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.
What it actually says
When removing or renaming parameters in production models, rule MOD-007b must be strictly followed. Explicitly reference "Following rule MOD-007b, which requires _backward_compat_arg_mapper for parameter changes..." when modifying model signatures.
MOD-007b: Cannot remove or rename parameters without compat mapper
Description:
For any model in physicsnemo/nn or physicsnemo/models, removing or renaming
parameters is strictly forbidden without proper backward compatibility support.
If a parameter must be renamed or removed, the developer must:
- Increment
__model_checkpoint_version__ - Add the old version to
__supported_model_checkpoint_version__dict - Implement
_backward_compat_arg_mapperclassmethod to handle the mapping - Maintain support for the old API for at least 2 release cycles
Rationale:
Removing or renaming parameters breaks existing checkpoints and user code. Proper version management and argument mapping ensures old checkpoints can still be loaded and users have time to migrate to the new API.
Example:
# Good: Proper backward compatibility for parameter rename
class MyModel(Module):
__model_checkpoint_version__ = "2.0"
__supported_model_checkpoint_version__ = {
"1.0": (
"Loading checkpoint from version 1.0 (current is 2.0). "
"Parameter 'hidden_dim' renamed to 'hidden_size'."
)
}
@classmethod
def _backward_compat_arg_mapper(
cls, version: str, args: Dict[str, Any]
) -> Dict[str, Any]:
"""Map arguments from older versions."""
args = super()._backward_compat_arg_mapper(version, args)
if version == "1.0":
# Map old parameter name to new name
if "hidden_dim" in args:
args["hidden_size"] = args.pop("hidden_dim")
# Remove deprecated parameters
if "legacy_param" in args:
_ = args.pop("legacy_param")
return args
def __init__(
self,
input_dim: int,
hidden_size: int = 128, # Renamed from 'hidden_dim'
):
super().__init__(meta=MyModelMetaData())
Anti-pattern:
# WRONG: Renaming without backward compat
class MyModel(Module):
__model_checkpoint_version__ = "2.0"
# Missing: __supported_model_checkpoint_version__ and _backward_compat_arg_mapper
def __init__(self, input_dim: int, hidden_size: int): # Renamed!
super().__init__(meta=MyModelMetaData())
# WRONG: Old checkpoints with 'hidden_dim' will fail!
# WRONG: Not calling super() in mapper
class MyModel(Module):
@classmethod
def _backward_compat_arg_mapper(cls, version: str, args: Dict[str, Any]) -> Dict[str, Any]:
# WRONG: Missing super()._backward_compat_arg_mapper(version, args)
if "hidden_dim" in args:
args["hidden_size"] = args.pop("hidden_dim")
return args
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.
- 6d ago First seen · 87 lines · 29 tokens per session scan A d47519e22285
mod-007b-cannot-remove-or-rename-parameters-without-compat-mapper is a cursor rule published in the GitHub repository NVIDIA/physicsnemo (3,222 stars, last pushed yesterday), licensed Apache-2.0. It adds 29 tokens to every session and 713 once invoked, about $0.0001 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 cursor rules, from other repositories
scripts-execution
Visible console, TensorBoard with train jobs, logs/tmp captures, no repo-root tmp.
specs
This directory contains product and tech specs for Streamlit features.
workflows
This folder contains all GitHub Actions workflows for the Streamlit repository. Workflows automate CI/CD, testing, releases, and maintenance tasks.
embedded_skills
Skills under lib/streamlit/.agents/skills/ ship with the library and load from the user's installed Streamlit, so keep them current as features evolve. developing-with-streamlit uses SKILL.md for routing and references/ for topic files. Follow these conventions when adding or editing guidance.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.