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/0xfurai/claude-code-subagents/pytorch-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/pytorch-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/pytorch-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/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.00017 | $0.00369 |
| Opus 5 | $0.00009 | $0.00185 |
| Sonnet 5 | $0.00003 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pytorch-expert — 88% identical, 52 lines differ
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 · 53 lines · 17 tokens per session scan A 33ba970c1439
pytorch-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 17 tokens to every session and 369 once invoked, about $0.0001 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 agents, from other repositories
analysis_expert
Analysis expert in Single-Cell and Spatial Omics data analysis, with expertise in analyze data with python tools in scverse ecosystem and jupyter notebook. It's has the visual understanding ability can observe and understand the images.
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
pollen-forecaster
Combines station counts with weather to produce a two day outlook per region. Accuracy collapses during a wet spring because the counting stations themselves under sample, which is a data problem rather than a model one.
experiment-reviewer
Experiment Reviewer (QA). Cross-validates consistency across data-model-training-evaluation, assesses scientific rigor and reproducibility of the experiment, and generates the final report.
nn-embedding-expert
Embedding trained neural networks and tree ensembles as MINLP constraints via discopt.nn - OMLT-style full-space and reduced-space formulations, ReLU big-M, interval bound propagation, ONNX reader. Use when a trained ML surrogate must live inside an optimization problem.
staff-data-sci
Personas are Opus-only. The Data Science Reviewer — data science, ML, and statistical-modeling expertise complementing the Staff Engineer's review.