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-003f-callback-functions-must-have-code-block-specificationgit 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.00467 | $0.00467 |
| Opus 5 | $0.00234 | $0.00234 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00047 | $0.00047 |
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.
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
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.
- 3d ago First seen · 67 lines · 467 tokens per session scan A 00b80e4e345a
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.
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.