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 skills/cxcscmu/skilllearnbench/pytorch-loss-implementationnpx skills add cxcscmu/SkillLearnBench --skill pytorch-loss-implementationgit clone --depth 1 https://github.com/cxcscmu/SkillLearnBenchWrote 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/skills/cxcscmu/skilllearnbench/pytorch-loss-implementation)<a href="https://agentmods.dev/skills/cxcscmu/skilllearnbench/pytorch-loss-implementation"><img src="https://agentmods.dev/badge/skills/cxcscmu/skilllearnbench/pytorch-loss-implementation.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.00597 |
| Opus 5 | $0.00009 | $0.00298 |
| Sonnet 5 | $0.00003 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
pytorch-loss-implementation 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PyTorch Loss Implementation
Key Concepts
1. Tensor Operations
import torch
# Sigmoid function
sigmoid_output = torch.sigmoid(input_tensor)
# Log function
log_output = torch.log(input_tensor)
# Mean reduction
mean_loss = loss.mean()
# Sum reduction
sum_loss = loss.sum()
2. Batch Processing
# Batch dimension handling
batch_size = tensor.shape[0]
x = tensor[:batch_size//2] # First half
y = tensor[batch_size//2:] # Second half
# Ensure same device and dtype
tensor = tensor.to(device=model.device, dtype=torch.float32)
3. Numerical Stability
Log-Sigmoid Stability
# Avoid: log(sigmoid(x)) can cause numerical issues
# Instead use:
stable_loss = torch.nn.functional.logsigmoid(x)
# Or manually:
loss = -torch.log(torch.sigmoid(x) + 1e-10)
Handling Small Values
# Add epsilon to avoid log(0)
safe_log = torch.log(value + 1e-8)
# Clamp to valid range
clamped = torch.clamp(value, min=1e-10, max=1.0)
4. Device Handling
# Ensure all tensors on same device
device = torch.device('cuda' if torch.cuda.is_available() else 'cpu')
tensor = tensor.to(device)
# Or get from model
device = next(model.parameters()).device
tensor = tensor.to(device)
Loss Function Pattern
def compute_loss(logits, labels, temperature=1.0, margin=0.5):
# 1. Normalize/compute rewards
rewards = logits / (sequence_length + 1e-8)
# 2. Compute differences
diff = temperature * rewards[:n//2] - temperature * rewards[n//2:] - margin
# 3. Apply objective
loss_per_pair = -torch.log(torch.sigmoid(diff) + 1e-10)
# 4. Reduce
loss = loss_per_pair.mean()
return loss
Debugging Tips
- Check tensor shapes at each step
- Use .detach() for inspecting values without affecting gradients
- Verify numerical stability with small inputs
- Test gradients with
loss.backward() - Print intermediate values for debugging
Performance Tips
- Use in-place operations where safe:
tensor.log_() - Avoid unnecessary cloning/copying
- Batch operations are faster than loops
- Use PyTorch functions over custom loops
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.
- 4d ago First seen · 102 lines · 17 tokens per session scan A d46f02386a7c
pytorch-loss-implementation is a skill published in the GitHub repository cxcscmu/SkillLearnBench (82 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 597 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-08-30.
Other skills, from other repositories
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
content-creator-setup
One-time onboarding for the content creator workflow — content pipeline stages, trend expiration, cross-platform cascades, heavy idea parking. After successful setup this skill is excluded from selection until the marker file is deleted.
idea-parking
Park interesting ideas for later consideration, resurface them periodically, and promote to commitments when ready.
routing-subtour-elimination
Subtour-elimination methods for TSP, VRP, pickup/dropoff routing, and routing MIPs with binary arc variables. Use when route-continuity constraints may permit disconnected cycles and the model needs MTZ constraints, flow-based connectivity constraints, DFJ subset cuts, or lazy/iterative subtour cuts.
scip-opt
SCIP optimization with PySCIPOpt. Use when facing an optimization problem with an objective, hard constraints, soft penalties, integer decisions, routing, assignment, scheduling, allocation, packing, capacity, inventory, or service-level rules. Prefer modeling and solving the problem with PySCIPOpt when it is…
ebcdic-overpunch-decoding
Reference for the EBCDIC "overpunch" / zoned-decimal sign convention where the units position of a numeric field is replaced with a letter that encodes both a digit and a sign. Useful when reading mainframe-style fixed-length tapes whose amount fields appear as digits followed by a letter (e.g. "0000000000123D" or…