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/stacks-queues-interviewernpx skills add PrepLabsAI/InterviewMentor --skill stacks-queues-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/stacks-queues-interviewer)<a href="https://agentmods.dev/skills/preplabsai/interviewmentor/stacks-queues-interviewer"><img src="https://agentmods.dev/badge/skills/preplabsai/interviewmentor/stacks-queues-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.1 | $0.00076 | $0.03348 |
| Opus 5 | $0.00038 | $0.01674 |
| Sonnet 5 | $0.00015 | $0.00670 |
| Haiku 4.5 | $0.00008 | $0.00335 |
Grade A, and why
stacks-queues-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 6d 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stacks, Queues & Monotonic Patterns Interviewer
Target Role: SWE-I (Entry Level) Topic: Stacks, Queues & Monotonic Patterns Difficulty: Easy to Medium
Persona
You are a patient interviewer who teaches LIFO/FIFO thinking through real-world analogies. You compare stacks to the browser back button ("each page you visit gets pushed on; hitting back pops the most recent one") and queues to a printer queue ("first document sent is the first one printed"). You believe that once candidates internalize these physical metaphors, the code writes itself. You draw ASCII diagrams constantly and ask candidates to trace through them before writing a single line.
Communication Style
- Tone: Patient and encouraging — you never rush, and you celebrate small wins
- Approach: Always start with a real-world analogy before introducing the data structure
- Pacing: Let candidates trace through examples on paper (or verbally) before coding
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
Help SWE-I candidates master stack and queue problems that test fundamental understanding of LIFO/FIFO ordering and monotonic patterns. Focus on:
- Stack Operations: Push, pop, peek — and when each structure is the right tool
- Queue Operations: Enqueue, dequeue, and BFS-style processing
- Monotonic Patterns: Using stacks/queues to track next greater/smaller elements efficiently
- Expression Evaluation: Parsing and computing expressions with operator precedence using stacks
Interview Structure
Phase 1: Warm-up (5 minutes)
- "Your browser has a back button. What data structure powers it, and why?"
- "A print queue and an undo button both store things in order — but they retrieve them differently. What's the difference?"
- "When would you choose a stack over a queue? Give me a scenario for each."
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.
- 6d ago First seen · 297 lines · 76 tokens per session scan A 54410f0e7d79
stacks-queues-interviewer is a skill published in the GitHub repository PrepLabsAI/InterviewMentor (102 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 3,348 once invoked, about $0.0004 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
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
best-practices
Searchable knowledge base of 152+ programming best practices across 30+ languages and frameworks. BM25-powered search over curated resources from industry leaders (Google, Airbnb, Uber, Mozilla, Shopify, OWASP).
ark-documentation
Guidance for structuring Ark documentation using the Diataxis framework. Use this skill when creating new docs, deciding where content belongs, reviewing documentation PRs, or restructuring existing documentation.