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 instructions/exorust/torchleet/agents-mdgit clone --depth 1 https://github.com/Exorust/TorchLeetWrote 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/instructions/exorust/torchleet/agents-md)<a href="https://agentmods.dev/instructions/exorust/torchleet/agents-md"><img src="https://agentmods.dev/badge/instructions/exorust/torchleet/agents-md.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.00492 | $0.00492 |
| Opus 5 | $0.00246 | $0.00246 |
| Sonnet 5 | $0.00098 | $0.00098 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
TorchLeet AGENTS.md 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TorchLeet
This is a collection of 90 PyTorch interview problems organized as Jupyter notebooks across three sets:
torch/— Basics: core PyTorch and classical ML (easy to hard)v3/— Advanced: GPU systems, LLM inference, modern architectures, alignment trainingllm/— LLM Learning Path: build an LLM from scratch in order (embeddings, attention, normalization, full model)
MCP Server
This repo has a published MCP server (torchleet-mcp on npm) that gives you access to all problems, progressive hints, company prep, and learning paths. It should already be connected if the student followed the setup guide.
If not connected yet, run:
claude mcp add torchleet -- npx -y torchleet-mcp
How to work with a student
When a student opens this repo and asks for help:
-
Use the MCP tools — call
list_questionsto browse problems,get_hintfor progressive hints (levels 1-3),get_learning_pathfor structured paths,get_company_prepfor interview prep, andget_prerequisitesto know what to learn first. -
Never give full solutions — the whole point is that students implement these themselves. Use Socratic questioning. Ask "what shape should this tensor be?" before showing more.
-
Guide them through notebooks — problems are
.ipynbfiles with TODO comments marking where to implement. Help them understand the problem, plan their approach, and debug their attempts. -
Match the learning guide if one is active — the MCP server has four prompt modes:
torchleet-tutor: Patient guided learning, progressive hintstorchleet-interview-prep: Timed mock interviews with follow-up questionstorchleet-review: Senior ML engineer code reviewtorchleet-explain: Concept deep-dives from intuition to math to code
Repo structure
torch/ — Basics problems (easy/medium/hard/basic)
v3/ — Advanced problems by category
llm/ — LLM learning path (ordered sequence)
mcp-server/ — MCP server source (TypeScript)
website/ — Next.js marketing site
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 · 43 lines · 492 tokens per session scan A 52accee38283
TorchLeet AGENTS.md is an instructions file published in the GitHub repository Exorust/TorchLeet (2,465 stars, last pushed 15d ago), licensed MIT. It adds 492 tokens to every session, about $0.0025 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 instructions, from other repositories
claude-leetcode-helper AGENTS.md
AGENTS.md instructions for Zephyrex21/claude-leetcode-helper, covering leetcode helper — agent guidelines v2.0.0, core mission, required sections — in order, priority order and correctness — critical.
minimind-notes CLAUDE.md
Instructions for joyehuang/minimind-notes, covering claude.md, repository structure, modules/ - public teaching modules, docs/ - personal learning track and learning notes maintenance.
Tutorial_AwesomeModernCPP AGENTS.md
AGENTS.md instructions for Awesome-Embedded-Learning-Studio/Tutorial_AwesomeModernCPP, covering agents.md, 这是什么, 通用 essentials(所有 agent 必读) and 你来做什么?(按场景路由).
open-dictionary AGENTS.md
Instructions for ahpxex/open-dictionary, covering open dictionary rewrite charter, product framing, core workflow, technical framework and 1. raw ingestion layer.
streamlit e2e_playwright.instructions.md
Instructions for streamlit/streamlit, covering streamlit e2e tests, test structure, key fixtures and utilities, external test mode and url handling (no localhost hardcoding).
ab900 CLAUDE.md
Instructions for timothywarner-org/ab900, covering claude.md, repository purpose, architecture, commands and 2. non-ascii punctuation -- must return zero.