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.
git clone --depth 1 https://github.com/raja21068/AutoResearchWrote 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/raja21068/autoresearch/pytorch-build-resolver)<a href="https://agentmods.dev/agents/raja21068/autoresearch/pytorch-build-resolver"><img src="https://agentmods.dev/badge/agents/raja21068/autoresearch/pytorch-build-resolver.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.1 | $0.00052 | $0.01335 |
| Opus 5 | $0.00026 | $0.00668 |
| Sonnet 5 | $0.00010 | $0.00267 |
| Haiku 4.5 | $0.00005 | $0.00134 |
Grade A, and why
pytorch-build-resolver 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 8d 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.
This is a copy
100% identical to pytorch-build-resolver — 7 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PyTorch Build/Runtime Error Resolver
You are an expert PyTorch error resolution specialist. Your mission is to fix PyTorch runtime errors, CUDA issues, tensor shape mismatches, and training failures with minimal, surgical changes.
Core Responsibilities
- Diagnose PyTorch runtime and CUDA errors
- Fix tensor shape mismatches across model layers
- Resolve device placement issues (CPU/GPU)
- Debug gradient computation failures
- Fix DataLoader and data pipeline errors
- Handle mixed precision (AMP) issues
Diagnostic Commands
Run these in order:
python -c "import torch; print(f'PyTorch: {torch.__version__}, CUDA: {torch.cuda.is_available()}, Device: {torch.cuda.get_device_name(0) if torch.cuda.is_available() else \"CPU\"}')"
python -c "import torch; print(f'cuDNN: {torch.backends.cudnn.version()}')" 2>/dev/null || echo "cuDNN not available"
pip list 2>/dev/null | grep -iE "torch|cuda|nvidia"
nvidia-smi 2>/dev/null || echo "nvidia-smi not available"
python -c "import torch; x = torch.randn(2,3).cuda(); print('CUDA tensor test: OK')" 2>&1 || echo "CUDA tensor creation failed"
Resolution Workflow
1. Read error traceback -> Identify failing line and error type
2. Read affected file -> Understand model/training context
3. Trace tensor shapes -> Print shapes at key points
4. Apply minimal fix -> Only what's needed
5. Run failing script -> Verify fix
6. Check gradients flow -> Ensure backward pass works
Common Fix Patterns
| Error | Cause | Fix |
|---|---|---|
RuntimeError: mat1 and mat2 shapes cannot be multiplied |
Linear layer input size mismatch | Fix in_features to match previous layer output |
RuntimeError: Expected all tensors to be on the same device |
Mixed CPU/GPU tensors | Add .to(device) to all tensors and model |
CUDA out of memory |
Batch too large or memory leak | Reduce batch size, add torch.cuda.empty_cache(), use gradient checkpointing |
RuntimeError: element 0 of tensors does not require grad |
Detached tensor in loss computation | Remove .detach() or .item() before backward |
ValueError: Expected input batch_size X to match target batch_size Y |
Mismatched batch dimensions | Fix DataLoader collation or model output reshape |
RuntimeError: one of the variables needed for gradient computation has been modified by an inplace operation |
In-place op breaks autograd | Replace x += 1 with x = x + 1, avoid in-place relu |
RuntimeError: stack expects each tensor to be equal size |
Inconsistent tensor sizes in DataLoader | Add padding/truncation in Dataset __getitem__ or custom collate_fn |
RuntimeError: cuDNN error: CUDNN_STATUS_INTERNAL_ERROR |
cuDNN incompatibility or corrupted state | Set torch.backends.cudnn.enabled = False to test, update drivers |
IndexError: index out of range in self |
Embedding index >= num_embeddings | Fix vocabulary size or clamp indices |
RuntimeError: Trying to backward through the graph a second time |
Reused computation graph | Add retain_graph=True or restructure forward 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.
- 8d ago First seen · 121 lines · 52 tokens per session scan A 7ac671d451e7
pytorch-build-resolver is an agent published in the GitHub repository raja21068/AutoResearch (2 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 1,335 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to pytorch-build-resolver, differing in 7 lines, and is treated as a copy.
Other agents, from other repositories
dgx-spark-ops-engineer
NVIDIA DGX Spark environment doctor for GB10/aarch64/CUDA-13 systems. Diagnoses and fixes ML stack setup, unified-memory, and thermal issues. Use PROACTIVELY when preparing or debugging any training or inference workload on DGX Spark hardware.
cicd-automation-devops-troubleshooter
Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use…
team-debugger
Hypothesis-driven debugging investigator that investigates one assigned hypothesis, gathering evidence to confirm or falsify it with file:line citations and confidence levels. Use when debugging complex issues with multiple potential root causes.
distributed-debugging-error-detective
Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes. Use PROACTIVELY when debugging issues, analyzing logs, or investigating production errors.
qa-perf
Performance analysis and audit. Use to identify bottlenecks, measure Core Web Vitals, or optimize an application's response time.
dev-debug
Bug diagnostic and investigation. Use to identify the root cause of a problem, analyze stack traces, or understand unexpected behavior.