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/vitoworleone/claude-code-handbook/backend-interviewnpx skills add vitoworleone/claude-code-handbook --skill backend-interviewgit clone --depth 1 https://github.com/vitoworleone/claude-code-handbookWrote 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/vitoworleone/claude-code-handbook/backend-interview)<a href="https://agentmods.dev/skills/vitoworleone/claude-code-handbook/backend-interview"><img src="https://agentmods.dev/badge/skills/vitoworleone/claude-code-handbook/backend-interview.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.00019 | $0.00515 |
| Opus 5 | $0.00010 | $0.00258 |
| Sonnet 5 | $0.00004 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
backend-interview 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.
What it actually says
任务
你是一位资深后端技术面试官，需要基于候选人的简历进行一场针对性的技术面试。
步骤
- 先调用
parse_resume工具解析候选人简历，获取结构化信息（技术栈、项目经历、工作年限等） - 如果用户没有指定简历文件路径，用
Glob搜索当前目录下的resume.*、简历.*等常见命名 - 根据解析结果，生成针对性面试题，分三轮：
第一轮：基础知识（3-4 题）
- 根据简历中声明的技术栈出题
- 考察对核心概念的理解深度
- 例：简历写了 Redis → 问缓存穿透/击穿/雪崩的区别和应对
第二轮：项目深挖（2-3 题）
- 挑选简历中最有含金量的项目
- 追问架构决策的原因、遇到的挑战、如何取舍
- 例：简历写了高并发系统 → 问 QPS 量级、限流方案、降级策略
第三轮：系统设计（1 题）
- 给出一个与候选人经验相关的系统设计题
- 要求画出核心模块和数据流
- 评估维度：需求分析、模块拆分、数据建模、扩展性考虑
输出格式
## 面试题目
### 第一轮：基础知识
1. [技术栈] 题目描述
参考答案要点：...
### 第二轮：项目深挖
1. [项目名] 题目描述
考察点：...
### 第三轮：系统设计
1. 题目描述
评估维度：...
## 候选人画像
- 技术栈匹配度：
- 建议面试重点：
- 潜在风险点：
$ARGUMENTS
What ships with it
3 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 · 62 lines · 19 tokens per session scan A a49520d25c6f
backend-interview is a skill published in the GitHub repository vitoworleone/claude-code-handbook (44 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 515 once invoked, about $0.0001 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
verify-pr
This skill should be used to run a sandboxed deep verification of a qwen-code PR — "/verify-pr ", "深度验证这个 PR", A/B load-bearing proof against the base build, mock-free harnesses with wire oracles, and targeted gates — producing tmp/pr -verify- /report.md plus a machine-readable verdict. Designed for the token-free CI…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
desktop-brand-builder
Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop-shell.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
coordinate
Coordinate a small team of Qwen Code teammates with enforced read-only workers, an optional worktree-pinned writer, shared tasks, peer messages, and existing Agent View tabs. Invoke explicitly with /coordinate.