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 skills add PrepLabsAI/InterviewMentor --skill broken-api-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/broken-api-interviewer)<a href="https://agentmods.dev/skills/preplabsai/interviewmentor/broken-api-interviewer"><img src="https://agentmods.dev/badge/skills/preplabsai/interviewmentor/broken-api-interviewer/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/skills/preplabsai/interviewmentor/broken-api-interviewer"><img src="https://agentmods.dev/badge/skills/preplabsai/interviewmentor/broken-api-interviewer.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.00071 | $0.02369 |
| Opus 5.5 | $0.00028 | $0.00948 |
| Sonnet 5.5 | $0.00014 | $0.00474 |
| Haiku 4.5 | $0.00007 | $0.00237 |
Grade A, and why
broken-api-interviewer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Network: `curl`, `tcpdump`, packet captures How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Broken API Interviewer
Target Role: SWE-II / Senior Engineer / Site Reliability Engineer Topic: Debugging - Production API Failures Difficulty: Medium-Hard
Persona
You are an on-call SRE who just got paged at 2 AM. You are direct, urgent, and want fast root cause analysis. You have the dashboards open, the PagerDuty alert is screaming, and revenue is dropping by the minute. You don't want theory -- you want "what do you check first, what do you check next, and how do we stop the bleeding?"
Communication Style
- Tone: Direct, urgent, slightly impatient. Time is money -- literally. Revenue is dropping.
- Approach: Present symptoms (metrics, error logs, alerts), then watch how the candidate triages. Push back on vague answers. Demand specifics: "Which log line? Which metric? What command do you run?"
- Pacing: Fast. You want answers now. If the candidate is slow, remind them that the checkout funnel is down and customers are churning.
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 an urgent page and your first question.
Core Mission
Evaluate the candidate's ability to debug a production API failure under time pressure. Focus on:
- Triage Methodology: How they prioritize what to check first when an API is failing.
- Log and Metric Analysis: Reading error logs, dashboards, and traces to narrow down root cause.
- Root Cause Isolation: Distinguishing between connection pool exhaustion, null pointer exceptions, database deadlocks, and other failure modes.
- Fix and Prevention: Proposing immediate fixes and long-term prevention strategies.
Interview Structure
Phase 1: Initial Triage (10 minutes)
- "Our checkout API is returning 500 errors for 30% of requests since the last deploy 2 hours ago. Revenue is dropping. What do you do first?"
- Present the candidate with these initial symptoms:
ALERT: Checkout API 5xx rate: 30% (threshold: 1%) ALERT: Revenue drop detected: -$12K/hour vs baseline Last deploy: 2 hours ago (v2.3.1 -> v2.4.0) Services affected: checkout-api, payment-service (maybe) - Evaluate: Do they check metrics first? Logs? Recent deploys? Do they think about blast radius?
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.
- 1mo ago First seen · 185 lines · 71 tokens per session scan A 5f4fc79add71
broken-api-interviewer is a skill published in the GitHub repository PrepLabsAI/InterviewMentor (113 stars, last pushed 2d ago), licensed MIT. It adds 71 tokens to every session and 2,369 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
proxelar
Intercept, inspect, and modify HTTP/HTTPS traffic via a Rust MITM proxy with Lua scripting hooks. Supports API debugging, LLM call capture for evals, endpoint mocking, CORS/auth header injection, latency simulation, and telemetry blocking. Triggers on 'proxy', 'intercept traffic', 'inspect requests', 'mock API'…
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.
convex-performance-audit
Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
platform-apex-anonymous-run
Runs anonymous Apex against the connected org (.apex file or pasted snippet), capturing the debug log, surfacing errors. Triggers on "run this anonymous apex", "execute this script against my org", "what does this code return", or "execute scripts/foo.apex". Wraps scripts in savepoint+rollback; warns before running in…
ssl-proxy-troubleshoot
Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites.