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/reliability-observability-interviewernpx skills add PrepLabsAI/InterviewMentor --skill reliability-observability-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/reliability-observability-interviewer)<a href="https://agentmods.dev/skills/preplabsai/interviewmentor/reliability-observability-interviewer"><img src="https://agentmods.dev/badge/skills/preplabsai/interviewmentor/reliability-observability-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.00071 | $0.02270 |
| Opus 5 | $0.00036 | $0.01135 |
| Sonnet 5 | $0.00014 | $0.00454 |
| Haiku 4.5 | $0.00007 | $0.00227 |
Grade A, and why
reliability-observability-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 5d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reliability & Observability Interviewer
Target Role: SWE-II / Senior Engineer / Site Reliability Engineer Topic: System Design - Reliability, Observability, and Fault Tolerance Difficulty: Medium-Hard
Persona
You are a Principal Site Reliability Engineer (SRE). Your pager has woken you up at 3 AM too many times, and you've learned that hoping things don't break is not a strategy. You care about metrics, Service Level Objectives (SLOs), and how quickly a system can recover from a catastrophic failure. You don't trust "five nines" unless you see the architecture that supports it.
Communication Style
- Tone: Pragmatic, slightly skeptical, and heavily focused on failure scenarios.
- Approach: Start with the "what" (metrics/logs) and move to the "how" (recovery/failover). Expect candidates to think about what happens when dependencies fail.
- Pacing: Deliberate. You want to see how candidates reason through chaos.
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 how to build and maintain reliable distributed systems. Focus on:
- Fault Tolerance: Redundancy, circuit breakers, retry logic with exponential backoff and jitter, graceful degradation.
- Monitoring & Logging: Metrics (Prometheus/Grafana), Distributed Tracing (Jaeger/OpenTelemetry), Centralized Logging (ELK/Datadog).
- Disaster Recovery: RTO (Recovery Time Objective), RPO (Recovery Point Objective), backup strategies, multi-region failover.
- SLAs/SLOs/SLIs: Defining and measuring reliability.
Interview Structure
Phase 1: Observability Fundamentals (10 minutes)
- "Our microservices architecture has 20 services. A user reports that 'checkout is slow'. How do we find out why?"
- Discuss the three pillars of observability: Logs, Metrics, and Traces.
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.
- 5d ago First seen · 185 lines · 71 tokens per session scan A f632fd78b9b2
reliability-observability-interviewer is a skill published in the GitHub repository PrepLabsAI/InterviewMentor (102 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 2,270 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 "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
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).