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/nedcodes-ok/cursorrules-collection/pytorchgit clone --depth 1 https://github.com/nedcodes-ok/cursorrules-collectionWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/pytorch)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/pytorch"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/pytorch.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00395 | $0.00395 |
| Opus 5 | $0.00198 | $0.00198 |
| Sonnet 5 | $0.00079 | $0.00079 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
pytorch 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 today.
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
PyTorch Rules
Model Architecture
- Use torch.nn.Module base class for all models
- Initialize layers in init, define forward pass in forward()
- Use meaningful layer names for debugging and model inspection
- Implement proper weight initialization for training stability
- Use torch.nn.Sequential for simple sequential models
Data Handling
- Use torch.utils.data.Dataset for custom datasets
- Implement len and getitem methods properly
- Use DataLoader with appropriate batch_size and num_workers
- Apply transforms consistently using torchvision.transforms
- Handle data augmentation in dataset transform pipeline
Training Loop
- Move model and data to same device (CPU/GPU)
- Use torch.no_grad() for validation and inference
- Clear gradients with optimizer.zero_grad() before backward pass
- Use mixed precision training with torch.cuda.amp for efficiency
- Implement proper checkpointing with state_dict
Memory Management
- Use torch.cuda.empty_cache() to clear GPU memory when needed
- Prefer in-place operations where possible (tensor.add_() vs tensor.add())
- Use gradient accumulation for large effective batch sizes
- Implement proper cleanup in exception handlers
- Monitor GPU memory usage with torch.cuda.memory_stats()
Model Deployment
- Use torch.jit.script or torch.jit.trace for production models
- Save models with torch.save(model.state_dict(), path)
- Use torch.hub for model sharing and distribution
- Implement proper error handling for device compatibility
- Test models on target deployment hardware
Best Practices
- Use torch.manual_seed() for reproducible results
- Validate tensor shapes throughout the pipeline
- Use appropriate loss functions and optimizers for your task
- Implement learning rate scheduling for better convergence
- Use tensorboard or wandb for training visualization
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.
- today First seen · 49 lines · 395 tokens per session scan A ca8673e24d06
pytorch is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (37 stars, last pushed 6mo ago), licensed MIT. It adds 395 tokens to every session, about $0.0020 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-09-03.
Other cursor rules, from other repositories
10-feature-development
Feature implementation workflow and engineering mindset.
11-template-conventions
Reusable building blocks shipped with this template - use them instead of writing new ones.
03-ui
UI, layout, theming and localization standards.
12-new-project
Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.
13-updating-project
Workflow for updating an existing project - dependency and SDK upgrades, migrations, refactors, bug fixes.
01-tech-stack
Android tech stack and project standards.