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 commands/huifer/claude-code-interview/listgit clone --depth 1 https://github.com/huifer/claude-code-interviewWhat 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.00009 | $0.00684 |
| Opus 5 | $0.00005 | $0.00342 |
| Sonnet 5 | $0.00002 | $0.00137 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
list 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 2d 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
公司列表
显示您正在申请的所有公司及其当前状态。
显示内容
对每个公司显示：
- 📌 公司名称
- 💼 目标职位
- 📊 申请状态
- 📍 当前阶段
- 📈 准备度评分
- 🎯 下一步行动
- 📅 面试安排（如有）
状态说明
申请状态:
preparing- 准备中applied- 已投递screening- 简历筛选interviewing- 面试中offer- 收到offerrejected- 已拒绝withdrawn- 已撤回
面试阶段:
resume_screen- 简历筛选online_assessment- 在线测试technical_round- 技术面试system_design- 系统设计behavioral- 行为面试onsite- 现场面试hr_round- HR面试
准备度评分:
- 90-100: 非常准备充分
- 75-89: 准备较好
- 60-74: 需要加强
- <60: 需要大量准备
示例输出
# 申请中的公司 (3)
## 1. Google
**职位**: Software Engineer III (L4)
**状态**: 🔄 interviewing
**阶段**: Technical Round (2/5)
**准备度**: 75/100 ⚠️
**面试安排**:
- 2025-01-15: Technical Interview (Online)
- 2025-01-20: System Design (Online)
**下一步**:
- [ ] 复习分布式系统
- [ ] 练习算法题
- [ ] 准备Google行为问题
---
## 2. Meta
**职位**: Software Engineer (E4)
**状态**: 📝 applied
**阶段**: Resume Screen
**准备度**: 65/100 ⚠️
**下一步**:
- [ ] /resume/variant meta - 创建定制简历
- [ ] /interview/prep meta - 生成准备指南
---
## 3. Amazon
**职位**: SDE II
**状态**: ✅ offer
**准备度**: 85/100 ✓
**下一步**:
- [ ] /offer/compare - 比较offer
快速操作
每个公司后面提供快速命令提示：
/company/view <name>- 查看详情/resume/variant <name>- 创建简历变体/interview/prep <name>- 面试准备/interview/simulate <name>- 模拟面试
统计信息
显示总数：
- 总申请公司数
- 各状态数量
- 本周面试安排
- 整体准备度
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.
- 2d ago First seen · 100 lines · 9 tokens per session scan A ed32fda10cce
list is a command published in the GitHub repository huifer/claude-code-interview (23 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 684 once invoked, about $0.0000 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.