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/reportgit 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.00013 | $0.00370 |
| Opus 5 | $0.00006 | $0.00185 |
| Sonnet 5 | $0.00003 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
report 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
不足分析报告生成
正在生成综合不足分析报告...
使用方法
/weakness/report [period]
时间周期 (period)
all- 全部历史（默认）week- 最近一周month- 最近一个月quarter- 最近一个季度
报告内容
报告将包含以下部分：
执行摘要
- 报告周期
- 生成时间
- 追踪不足总数
- 重复出现数量
- 未改善数量
🔴 高频重复问题
- 列出出现频率最高的问题
- 显示出现次数、严重性、趋势
- 说明影响范围
📊 类别分布
- 按类别统计不足数量
- 显示占比和优先级均值
- 表格形式呈现
📈 趋势分析
- 各类不足的出现频率趋势
- 改善进展统计
- 状态转换情况
🎯 改进计划
- 按周分解的改进任务
- 优先级排序
- 预期成果
📊 统计图表
- 不足优先级分布（饼图）
- 出现频率分布（柱状图）
- 改善进度趋势（折线图）
🔗 相关面试
- 列出相关的面试记录
- 便于回顾和对比
请指定时间周期（all/week/month/quarter），或直接按回车生成全部历史报告。
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 · 64 lines · 13 tokens per session scan A b6a6ab86e3ce
report is a command published in the GitHub repository huifer/claude-code-interview (23 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 370 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 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.