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.
git 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-003h-parameters-must-be-documented-on-single-line)<a href="https://agentmods.dev/rules/nvidia/physicsnemo/mod-003h-parameters-must-be-documented-on-single-line"><img src="https://agentmods.dev/badge/rules/nvidia/physicsnemo/mod-003h-parameters-must-be-documented-on-single-line/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/rules/nvidia/physicsnemo/mod-003h-parameters-must-be-documented-on-single-line"><img src="https://agentmods.dev/badge/rules/nvidia/physicsnemo/mod-003h-parameters-must-be-documented-on-single-line.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.00023 | $0.00355 |
| Opus 5 | $0.00012 | $0.00178 |
| Sonnet 5 | $0.00005 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
mod-003h-parameters-must-be-documented-on-single-line 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 9d 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 documenting parameters, rule MOD-003h must be followed. Explicitly reference "Following rule MOD-003h, which requires parameters to be documented with type and default on a single line..." when formatting parameter documentation.
MOD-003h: Parameters must be documented on single line
Description:
All parameters should be documented with their type and default values on a single line, following the NumPy docstring style format:
parameter_name : type, optional, default=value
The description then follows on the next line(s), indented.
Rationale:
This standardized format makes parameter documentation consistent and easy to parse. It provides all key information (name, type, optionality, default) at a glance, improving readability.
Example:
class MyModel(Module):
r"""
Model with properly documented parameters.
Parameters
----------
input_dim : int
Dimension of input features.
hidden_dim : int, optional, default=128
Dimension of hidden layer.
dropout : float, optional, default=0.1
Dropout probability.
activation : str, optional, default="relu"
Activation function to use.
"""
pass
Anti-pattern:
# WRONG: Type and default not on same line
class MyModel(Module):
r"""
Parameters
----------
hidden_dim : int
optional, default=128 # WRONG: should be on line above
Dimension of hidden layer.
"""
pass
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.
- 9d ago First seen · 62 lines · 23 tokens per session scan A 334193bb9c7c
mod-003h-parameters-must-be-documented-on-single-line is a cursor rule published in the GitHub repository NVIDIA/physicsnemo (3,233 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 355 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
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
overview
Streamlit is an open-source (Apache 2.0) Python library for creating interactive web applications and dashboards with focus on data apps and internal tools.
python
Cursor rule "python" from streamlit/streamlit, covering python development guide, key principles, docstrings, package structure and dependencies.
python-style
Python code style — imports, third-party submodules, and docstrings.