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-003j-docstrings-should-include-examples-sectiongit 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.00023 | $0.00501 |
| Opus 5 | $0.00012 | $0.00251 |
| Sonnet 5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
mod-003j-docstrings-should-include-examples-section 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 docstrings, rule MOD-003j should be followed. Explicitly reference "Following rule MOD-003j, which encourages an Examples section that CI will automatically test..." when adding examples.
MOD-003j: Docstrings should include Examples section
Description:
Docstrings are strongly encouraged to have an Examples section that
demonstrates basic construction and usage of the model. These example sections
serve as both documentation and tests, as our CI system automatically tests
these code sections for correctness when present.
Examples should be executable Python code showing typical use cases, including model instantiation, input preparation, and forward pass execution. The examples should use realistic tensor shapes and demonstrate key features of the model.
Rationale:
Example sections provide immediate value to users by showing concrete usage patterns. By automatically testing these examples in CI, we ensure that documentation stays synchronized with code and that examples remain correct as the codebase evolves. This catches API changes that would otherwise break user code without warning.
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
--------
>>> import torch
>>> from physicsnemo.models import MyEncoder
>>>
>>> # Create model
>>> model = MyEncoder(input_dim=784, output_dim=128)
>>>
>>> # Process a batch
>>> x = torch.randn(32, 784)
>>> output = model(x)
>>> output.shape
torch.Size([32, 128])
"""
pass
Anti-pattern:
# Not wrong, but strongly discouraged - no Examples section
class MyEncoder(Module):
r"""
A simple encoder network.
Parameters
----------
input_dim : int
Dimension of input features.
"""
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 · 85 lines · 23 tokens per session scan A ef78898604eb
mod-003j-docstrings-should-include-examples-section is a cursor rule published in the GitHub repository NVIDIA/physicsnemo (3,211 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 501 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.
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.