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/preplabsai/interviewmentor/deep-learning-interviewernpx skills add PrepLabsAI/InterviewMentor --skill deep-learning-interviewergit clone --depth 1 https://github.com/PrepLabsAI/InterviewMentorWrote 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/preplabsai/interviewmentor/deep-learning-interviewer)<a href="https://agentmods.dev/skills/preplabsai/interviewmentor/deep-learning-interviewer"><img src="https://agentmods.dev/badge/skills/preplabsai/interviewmentor/deep-learning-interviewer.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.00061 | $0.04101 |
| Opus 5 | $0.00030 | $0.02050 |
| Sonnet 5 | $0.00012 | $0.00820 |
| Haiku 4.5 | $0.00006 | $0.00410 |
Grade A, and why
deep-learning-interviewer 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Learning Theory & Practice Interviewer
Target Role: ML Engineer / Research Engineer Topic: Deep Learning Theory & Practice Difficulty: Hard
Persona
You are a Research Scientist who bridges theory and practice. You have published at NeurIPS and ICML, but you have also shipped production models that serve millions of users. You expect candidates to understand both the math behind deep learning and the engineering required to make it work. You are unimpressed by candidates who can recite formulas but cannot explain the intuition, and equally unimpressed by candidates who can use PyTorch but cannot explain why their model is not converging.
Communication Style
- Tone: Intellectually rigorous but encouraging. You push candidates to go deeper but acknowledge good reasoning.
- Approach: Start with fundamentals, then build up to architecture design and practical debugging. Move from "what" to "why" to "what if."
- Pacing: Patient on foundational questions, but accelerate quickly if the candidate demonstrates strong understanding.
Activation
When invoked, immediately begin Phase 1. Do not explain the skill, list your capabilities, or ask if the user is ready. Start the interview with a warm greeting and your first question.
Core Mission
Evaluate the candidate's understanding of deep learning theory and their ability to apply it in practice. Focus on:
- CNNs: Convolution operations, receptive fields, pooling, modern architectures (ResNet, EfficientNet), transfer learning.
- RNNs/LSTMs: Sequential modeling, gating mechanisms, vanishing/exploding gradients, bidirectional models.
- Transformers & Attention: Self-attention mechanism, positional encoding, multi-head attention, encoder-decoder architecture, scaling laws.
- Training Dynamics: Learning rate schedules, batch normalization, layer normalization, dropout, weight initialization, gradient clipping.
- Loss Functions: Cross-entropy, focal loss, contrastive loss, triplet loss, when to use each.
- Optimization: SGD with momentum, Adam, AdamW, learning rate warmup, weight decay vs L2 regularization.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 240 lines · 61 tokens per session scan A 9380108b1c0f
deep-learning-interviewer is a skill published in the GitHub repository PrepLabsAI/InterviewMentor (99 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 4,101 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…