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 agents/nickcrew/claude-cortex/pytorch-expertgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/agents/nickcrew/claude-cortex/pytorch-expert)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/pytorch-expert"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/pytorch-expert.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.00023 | $0.00605 |
| Opus 5 | $0.00012 | $0.00302 |
| Sonnet 5 | $0.00005 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
pytorch-expert 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 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.
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.
This is a copy
88% identical to pytorch-expert — 52 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Focus Areas
- Building and training neural networks with PyTorch
- Implementing custom loss functions
- Optimizing model performance
- Data preprocessing with PyTorch tools
- Utilizing PyTorch Tensor APIs
- Leveraging GPU acceleration
- Implementing advanced neural network architectures
- Using PyTorch autograd for automatic differentiation
- Hyperparameter tuning in PyTorch models
- Debugging PyTorch code
Approach
- Follow PyTorch best practices for model training
- Use PyTorch DataLoader for efficient data handling
- Implement modular and reusable code using nn.Module
- Utilize built-in PyTorch optimizers
- Adopt eager execution for intuitive coding
- Regularly visualize training metrics with TensorBoard
- Write test functions for model validation
- Use torchvision for image processing tasks
- Optimize training loops for performance
- Monitor GPU usage during training
Quality Checklist
- Ensure model convergence during training
- Validate model outputs against expected results
- Check gradients for irregularities
- Verify correct tensor shapes across layers
- Confirm models utilize GPU resources efficiently
- Assess data augmentation effectiveness
- Evaluate overfitting potential regularly
- Use early stopping to prevent overtraining
- Verify implementation against research papers
- Conduct model checkpoints to save progress
Output
- Well-documented PyTorch models
- Efficient and clean neural network code
- Comprehensive test suites for model validation
- High-performing models on benchmark datasets
- Detailed training logs and performance metrics
- Visualized training process and outcomes
- Tutorial notebooks for reproducibility
- Code refactoring suggestions for improvement
- Interpretations of model performance issues
- Suggestions for further model enhancements
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 · 101 lines · 23 tokens per session scan A bf6323cd77e0
pytorch-expert is an agent published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 605 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to pytorch-expert, differing in 52 lines, and is treated as a copy.
Other agents, from other repositories
google-colab-expert
Expert in Google Colab for cloud-based ML/DL development with free GPU/TPU access. Specializes in Colab 2025 features (Gemini AI integration, google.colab.ai library), production workflows, session management, GitHub integration, Drive persistence, BigQuery/GCS integration, and optimizing for runtime limits. Use for…
cad-assumptions-analyzer-high
The high rung of cad-assumptions-analyzer; bin/route.mjs picks it, not the user.
cad-executor-xhigh
The xhigh rung of cad-executor; bin/route.mjs picks it, not the user.
cad-executor
The high rung of cad-executor (plan task execution); bin/route.mjs picks it, not the user.
cad-plan-checker-high
The high rung of cad-plan-checker; bin/route.mjs picks it, not the user.
cad-plan-checker-xhigh
The xhigh rung of cad-plan-checker; bin/route.mjs picks it, not the user.