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-003a-missing-or-incomplete-docstringgit clone --depth 1 https://github.com/NVIDIA/physicsnemoWhat 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.00034 | $0.00416 |
| Opus 5 | $0.00017 | $0.00208 |
| Sonnet 5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
mod-003a-missing-or-incomplete-docstring 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.
What it actually says
When writing model or layer documentation, rule MOD-003a must be followed. Explicitly reference "Following rule MOD-003a, which requires comprehensive docstrings following all MOD-003 sub-rules..." when creating documentation.
MOD-003a: Missing or incomplete docstring for model/layer code
Description:
Every new model or modification of any model code should be documented with a comprehensive docstring following all the sub-rules MOD-003b through MOD-003k. All docstrings should be written in the NumPy style and adopt formatting to be compatible with our Sphinx restructured text (RST) documentation.
Rationale:
Comprehensive and well-formatted documentation is essential for scientific software. It enables users to understand model capabilities, expected inputs, and outputs without inspecting source code.
Example:
class MyEncoder(Module):
r"""
A simple encoder network.
Parameters
----------
input_dim : int
Dimension of input features.
output_dim : int
Dimension of output features.
Forward
-------
x : torch.Tensor
Input tensor of shape :math:`(B, D_{in})`.
Outputs
-------
torch.Tensor
Output tensor of shape :math:`(B, D_{out})`.
Examples
--------
>>> model = MyEncoder(input_dim=784, output_dim=128)
>>> x = torch.randn(32, 784)
>>> output = model(x)
>>> output.shape
torch.Size([32, 128])
"""
pass
Anti-pattern:
# WRONG: Missing all required sections
class BadEncoder(Module):
'''A simple encoder.''' # Wrong quotes, no sections
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.
- 2d ago First seen · 66 lines · 34 tokens per session scan A 0eee4a3ccf6f
mod-003a-missing-or-incomplete-docstring is a cursor rule published in the GitHub repository NVIDIA/physicsnemo (3,211 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 416 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-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.
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.
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.
skills
This file provides guidance to AI coding agents (Claude Code, Cursor, Copilot, etc.) when working with skills in this repository.