reflect

reflect is a command for coding agents from noamseg/interview-coach-skill. It costs 0 tokens per session (1,331 once invoked), scanned A, original, MIT.

A retrospective command for reviewing an interview-search coaching period after it ends or pauses. It looks back at recorded scores, interview results, practice progress, and changes in prepared stories.

In plain words
What is it for?
Use it after accepting a job, pausing the search, completing many coaching sessions without recent activity, or asking what you learned and how you performed overall.
Why use it?
It helps turn a long job search into lessons and a clear account of what improved, what remained difficult, and what to do next.

Command

About the project

Interview Coach is a Claude Code-based coaching system for the full job-search process, including job-description analysis, application materials, interview practice, answer evaluation, and offer negotiation. It is intended for job seekers who want tailored feedback and structured preparation based on their own experience and interview transcripts. Its catalogue entry consists of commands, a setting, and a skill that provide the coaching workflows.

noamseg/interview-coach-skill · 2,092 stars · on GitHub

Install

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.

agentmods
npx agentmods add commands/noamseg/interview-coach-skill/reflect
Clone the repo
git clone --depth 1 https://github.com/noamseg/interview-coach-skill

Wrote 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.

agentmods badge for reflect

README.md
[![agentmods](https://agentmods.dev/badge/commands/noamseg/interview-coach-skill/reflect.svg)](https://agentmods.dev/commands/noamseg/interview-coach-skill/reflect)
Your own site
<a href="https://agentmods.dev/commands/noamseg/interview-coach-skill/reflect"><img src="https://agentmods.dev/badge/commands/noamseg/interview-coach-skill/reflect.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,331 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01331
Opus 5 $0.00000 $0.00665
Sonnet 5 $0.00000 $0.00266
Haiku 4.5 $0.00000 $0.00133

Measured 5d ago against content hash f6bb60563c37, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

reflect 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.

references/commands/reflect.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

reflect — Post-Search Retrospective Workflow

Closes the loop on a coaching engagement. Run when the candidate has accepted an offer, decided to pause their search, or wants to take stock after a sustained effort.

When to Trigger

Suggest reflect when:

  • The candidate reports accepting an offer
  • The candidate says they're pausing or stopping their search
  • 8+ sessions have been completed with no recent activity
  • The candidate asks "what did I learn?" or "how did I do overall?"

Sequence

  1. Acknowledge the milestone. Whether it's an offer, a pause, or a pivot, name it: "You've been at this for [duration]. Let's look at the full arc." Don't skip this — the candidate deserves recognition for the work they put in.
  2. Pull the full data. Review all of coaching_state.md: score history, outcome log, storybank evolution, drill progression, Active Coaching Strategy.
  3. Narrate the journey. This is not a progress report — it's a story about growth:
    • Where did they start? (kickoff baseline)
    • What were the biggest breakthroughs? (inflection points from score history)
    • What was hardest to improve? (persistent patterns)
    • What's genuinely different about how they interview now vs. when they started?
    • Initial vs. final self-assessment comparison: Pull the candidate's initial concerns and self-assessment from kickoff (biggest concern, interview readiness assessment) and compare to their most recent progress calibration data. Show the delta: "You started thinking your biggest weakness was [X]. Turns out it was [Y]. Your initial self-assessment was [over/under/accurate] — and your calibration improved to [current accuracy]." This bookend comparison makes growth tangible.
  4. Extract transferable lessons. What did they learn that applies beyond this job search?
    • Communication skills that transfer to the job itself — the interview coaching skills map directly to Ethan Evans' Magic Loop framework, step 2: "Tell the right people about your work" (via Lenny's Newsletter). The candidate has practiced structured communication, positioning, and storytelling under pressure — these are the exact skills that drive visibility and career growth in the new role.
    • Self-awareness insights (self-assessment calibration patterns)
    • Storytelling ability that helps in presentations, stakeholder management, etc.
    • Wes Kao's concept of "minimum viable opinions" (MOPs, via Lenny's Podcast) applies to the transition into a new role: form and articulate provisional opinions early, even before having full context. The structured thinking skills developed through interview coaching — framing, evidence-based reasoning, acknowledging uncertainty — are exactly what MOPs require.
  5. If they got an offer: What made the difference? Which dimensions were strongest in the interviews that advanced? Which stories landed? What changed between early rejections and later advances?
  6. If they didn't get an offer (or are pausing): Honest diagnosis without blame. What are the remaining gaps? Are they coachable with more practice, or do they suggest a targeting adjustment? What should they focus on if/when they resume?
  7. Archive and close.

Read the full file on GitHub · 104 lines

Changes

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.

  1. 5d ago First seen · 104 lines · 0 tokens per session scan A f6bb60563c37

Subscribe to this mod's changes

reflect is a command published in the GitHub repository noamseg/interview-coach-skill (2,092 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,331 tokens. 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.