mod-003f-callback-functions-must-have-code-block-specification

A documentation rule for callback functions, which are functions passed to other code to be called later. It requires a separate code block showing the callback’s required inputs and return value.

In plain words
What is it for?
Use it when documenting callback parameters or other arguments with detailed type or interface requirements.
Why use it?
A code block makes complex function requirements clearer than describing them only in a parameter list.

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-003f-callback-functions-must-have-code-block-specification
Clone the repo
git clone --depth 1 https://github.com/NVIDIA/physicsnemo

Made for: Cursor.

Per session 467 This file is loaded in full into every session.
When invoked 467 The same file — it is already loaded in full.
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.00467 $0.00467
Opus 5 $0.00234 $0.00234
Sonnet 5 $0.00093 $0.00093
Haiku 4.5 $0.00047 $0.00047

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

Security

Grade A, and why

mod-003f-callback-functions-must-have-code-block-specification 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 3d 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-003f-callback-functions-must-have-code-block-specification.mdc · 67 lines

What it actually says

When documenting callback functions or complex API parameters, rule MOD-003f must be followed. Explicitly reference "Following rule MOD-003f, which requires callback functions to have a ..code-block:: specification..." when adding these specifications.

MOD-003f: Callback functions must have code-block specification

Description:

For arguments or variables that are callback functions (e.g. Callable), the docstring should include a clear separated ..code-block:: that specifies the required signature and return type of the callback function. This is not only true for callback functions, but for any type of parameters or arguments that has some complex type specification or API requirements.

The explanation code block should be placed in the top or bottom section of the docstrings, but not in the Parameters or Forward or Outputs sections, for readability and clarity.

Rationale:

Callback functions have complex type signatures that are difficult to express clearly in the Parameters section alone. A dedicated code-block provides a clear visual reference for the expected signature, making it much easier for users to implement compatible callbacks.

Example:

class MyModel(Module):
    r"""
    Model with callback function.

    .. code-block:: python

        def preprocess_fn(x: torch.Tensor) -> torch.Tensor:
            '''Preprocessing function signature.'''
            ...
            return y

    where ``x`` is input of shape :math:`(B, D_{in})` and ``y`` is output
    of shape :math:`(B, D_{out})`.

    Parameters
    ----------
    preprocess_fn : Callable[[torch.Tensor], torch.Tensor], optional
        Optional preprocessing function. See code block above for signature.
    """
    pass

Anti-pattern:

# WRONG: No code-block specification for callback
class MyModel(Module):
    r"""
    Parameters
    ----------
    preprocess_fn : Callable[[torch.Tensor], torch.Tensor], optional
        Preprocessing function.  # No specification of signature!
    """
    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. 3d ago First seen · 67 lines · 467 tokens per session scan A 00b80e4e345a

Subscribe to this mod's changes

mod-003f-callback-functions-must-have-code-block-specification is a cursor rule published in the GitHub repository NVIDIA/physicsnemo (3,211 stars, last pushed yesterday), licensed Apache-2.0. It adds 467 tokens to every session, about $0.0023 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.