mod-003j-docstrings-should-include-examples-section

A documentation rule for model docstrings, which are explanatory notes attached to model code. It encourages an Examples section containing executable Python code that shows how to create and use the model.

In plain words
What is it for?
Use it when documenting models, including their construction, input tensors, forward pass, and typical usage.
Why use it?
The examples give users a practical starting point and can be automatically tested by continuous integration, helping keep documentation accurate.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/nvidia/physicsnemo/mod-003j-docstrings-should-include-examples-section
Clone the repo
git clone --depth 1 https://github.com/NVIDIA/physicsnemo

Made for: Cursor.

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 501 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash ef78898604eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.cursor/rules/mod-003j-docstrings-should-include-examples-section.mdc · 85 lines

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
Changes

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.

  1. 2d ago First seen · 85 lines · 23 tokens per session scan A ef78898604eb

Subscribe to this mod's changes

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.