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/loulanyue/awesome-claude-notesWrote 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/loulanyue/awesome-claude-notes/pytorch-build-resolver)<a href="https://agentmods.dev/agents/loulanyue/awesome-claude-notes/pytorch-build-resolver"><img src="https://agentmods.dev/badge/agents/loulanyue/awesome-claude-notes/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.
<a href="https://agentmods.dev/agents/loulanyue/awesome-claude-notes/pytorch-build-resolver"><img src="https://agentmods.dev/badge/agents/loulanyue/awesome-claude-notes/pytorch-build-resolver.svg" alt="Reviewed on agentmods" width="80" 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.01389 |
| Opus 5.5 | $0.00021 | $0.00556 |
| Sonnet 5.5 | $0.00010 | $0.00278 |
| Haiku 4.5 | $0.00005 | $0.00139 |
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 1mo 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- pytorch-build-resolver — 100% identical, 7 lines differ
- pytorch-build-resolver — 100% identical, 7 lines differ
- pytorch-build-resolver — 97% identical, 10 lines differ
- pytorch-build-resolver — 92% identical, 26 lines differ
- pytorch-build-resolver — 91% identical, 24 lines differ
- pytorch-build-resolver — 89% identical, 21 lines differ
How it starts
The opening of the file, as written. The whole thing — 128 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.
- 1mo ago First seen · 128 lines · 52 tokens per session scan A c00798dd62c0
pytorch-build-resolver is an agent published in the GitHub repository loulanyue/awesome-claude-notes (271 stars, last pushed 19d ago), licensed MIT. It adds 52 tokens to every session and 1,389 once invoked, about $0.0002 per session on Opus 5.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
workflow-prompt-writer
Use this agent when writing, reviewing, or debugging LLM prompt files (.prompt). Specializes in Liquid.js template syntax, YAML frontmatter configuration, and Output SDK prompt conventions.
integration-prober
External service integration verifier. Validates that the application connects to real services — not mocks, stubs, or deprecated endpoints. Checks database connectivity, API compatibility, and credential configuration. Read-only — produces findings, never code.
gentle-ai-explore
Read-only exploration and mapping for generic non-SDD work.
patch-generator
Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.
openrouter-specialist
Expert consultant for OpenRouter API integration, model routing strategies, cost optimization, and multi-provider management. Use proactively for OpenRouter architecture analysis, model selection strategies, routing optimization, and integration pattern recommendations. Provides consultation and recommendations only …
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.