pytorch-build-resolver

pytorch-build-resolver is an agent for Claude Code from Fmarzochi/EGC. It costs 52 tokens per session (1,345 once invoked), scanned A, a copy of pytorch-build-resolver, Apache-2.0.

A PyTorch troubleshooting assistant for machine-learning programs that run training or inference. PyTorch is a Python library for building and running neural networks.

In plain words
What is it for?
Use it when PyTorch training or inference fails, particularly when checking CUDA, cuDNN, installed packages, or GPU tensor creation.
Why use it?
It helps diagnose crashes caused by tensor shapes, CPU/GPU placement, gradients, data loading, CUDA, or mixed-precision calculations.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it when PyTorch training or inference fails, particularly when checking CUDA, cuDNN, installed packages, or GPU tensor creation.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/fmarzochi/egc/pytorch-build-resolver
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Fmarzochi/EGC

Made for: Claude Code.

Wrote 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.

agentmods badge for pytorch-build-resolver

README.md
[![agentmods](https://agentmods.dev/badge/agents/fmarzochi/egc/pytorch-build-resolver/github.svg)](https://agentmods.dev/agents/fmarzochi/egc/pytorch-build-resolver)
Your own site
<a href="https://agentmods.dev/agents/fmarzochi/egc/pytorch-build-resolver"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/pytorch-build-resolver/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for pytorch-build-resolver

Your own site · 80×15
<a href="https://agentmods.dev/agents/fmarzochi/egc/pytorch-build-resolver"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/pytorch-build-resolver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,345 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.01345
Opus 5 $0.00026 $0.00673
Sonnet 5 $0.00010 $0.00269
Haiku 4.5 $0.00005 $0.00135

Measured 5d ago against content hash 9564b29ed3bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 5d 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.

Origin

This is a copy

97% identical to pytorch-build-resolver — 10 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.

agents/pytorch-build-resolver.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 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

  1. Diagnose PyTorch runtime and CUDA errors
  2. Fix tensor shape mismatches across model layers
  3. Resolve device placement issues (CPU/GPU)
  4. Debug gradient computation failures
  5. Fix DataLoader and data pipeline errors
  6. 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

Read the full file on GitHub · 122 lines

Changes

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.

  1. 5d ago First seen · 122 lines · 52 tokens per session scan A 9564b29ed3bb

Subscribe to this mod's changes

pytorch-build-resolver is an agent published in the GitHub repository Fmarzochi/EGC (49 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 1,345 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to pytorch-build-resolver, differing in 10 lines, and is treated as a copy.

Related

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.

wshobson/agents · 63 tokens

timps_kubernetes_navigator

Diagnose Kubernetes workloads: pods, services, ingress, RBAC, resources, network policies. Outputs fix YAML and Helm/Kustomize patches. Use the timpskubernetesnavigator MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.

Sandeeprdy1729/timps-swarm · 64 tokens

ui-debugger

Evidence-driven frontend debugger for a running localhost app. Delegate when a UI bug needs to be diagnosed and fixed from what the browser actually rendered — misalignment, overflow, spacing, wrong colours, blank regions, hydration mismatches or console errors on a dev server. Requires the dev server to be running…

soumyachk101/VibeLens · 74 tokens

ecc-pytorch-build-resolver

PyTorch runtime, CUDA, and training error resolution specialist. Fixes tensor shape mismatches, device errors, gradient issues, DataLoader problems, and mixed precision failures with minimal changes. Use when PyTorch training or inference crashes.

sakuradairong/omp-config · 53 tokens

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens