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-002c-remove-deprecated-model-from-codebasegit 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.00026 | $0.00439 |
| Opus 5 | $0.00013 | $0.00219 |
| Sonnet 5 | $0.00005 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade B, and why
mod-002c-remove-deprecated-model-from-codebase scanned grade B with 1 finding 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 yesterday.
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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
# v0.5.0: Model exists without warnings What it actually says
When removing deprecated models, rule MOD-002c must be followed. Explicitly reference "Following rule MOD-002c, which states that a model can only be deleted after at least 1 release cycle in pre-deprecation..." when removing code.
MOD-002c: Remove deprecated model from codebase
Description:
After staying in the pre-deprecation stage (Stage 3) for at least 1 release cycle, the model class is considered deprecated (Stage 4). It can then be deleted from the codebase.
A model class cannot be deleted without first spending at least 1 release cycle in the pre-deprecation stage with proper deprecation warnings (see MOD-002b).
Rationale:
This ensures users have sufficient warning and time to migrate their code to newer alternatives. Premature deletion of models would break user code without adequate notice, violating the framework's commitment to stability.
Example:
# Good: Model spent 1 release cycle in pre-deprecation (v0.5.0 with warnings)
# Now in v0.6.0, can be deleted
# File: physicsnemo/models/old_diffusion.py - DELETED
# Release timeline:
# v0.5.0: Added deprecation warnings (Stage 3)
# v0.6.0: Model can be safely removed (Stage 4)
Anti-pattern:
# WRONG: Deleting model without deprecation period
# v0.5.0: Model exists without warnings
# v0.6.0: Model deleted - BREAKS USER CODE!
# WRONG: Breaking changes in production without deprecation cycle
# File: physicsnemo/models/diffusion.py
class DiffusionModel(Module):
def __init__(self, new_required_param): # Breaking change!
# Changed API without deprecation warning - breaks user code
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.
- yesterday First seen · 51 lines · 26 tokens per session scan B cb33716ed8da
mod-002c-remove-deprecated-model-from-codebase is a cursor rule published in the GitHub repository NVIDIA/physicsnemo (3,209 stars, last pushed 3d ago), licensed Apache-2.0. It adds 26 tokens to every session and 439 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). 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.