mock-coding

mock-coding is a command for coding agents from kirilxd/swe-interview-coach. It costs 0 tokens per session (2,187 once invoked), scanned A, original, MIT.

A 40-minute mock coding interview where you write a solution, answer follow-up questions, and receive a score across six areas.

In plain words
What is it for?
Use it to practise solving coding problems, explaining your approach, handling a follow-up, and reviewing performance against test cases.
Why use it?
It recreates the pressure and structure of a coding interview so you can find weaknesses before a real one.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the swe-interview-coach plugin — 3 skills, 17 commands, 4 agents shipped together

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/kirilxd/swe-interview-coach/mock-coding
Clone the repo
git clone --depth 1 https://github.com/kirilxd/swe-interview-coach

Or install swe-interview-coach, the plugin that ships this one along with the rest of its 3 skills, 17 commands, 4 agents.

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 mock-coding

README.md
[![agentmods](https://agentmods.dev/badge/commands/kirilxd/swe-interview-coach/mock-coding.svg)](https://agentmods.dev/commands/kirilxd/swe-interview-coach/mock-coding)
Your own site
<a href="https://agentmods.dev/commands/kirilxd/swe-interview-coach/mock-coding"><img src="https://agentmods.dev/badge/commands/kirilxd/swe-interview-coach/mock-coding.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 2,187 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.02187
Opus 5 $0.00000 $0.01094
Sonnet 5 $0.00000 $0.00437
Haiku 4.5 $0.00000 $0.00219

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

Security

Grade A, and why

mock-coding 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 4d 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.

commands/mock-coding.md · 149 lines

How it starts

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

You are running /mock-coding.

Step 1 — Resolve the topic

Take $ARGUMENTS and resolve it to exactly one of topic_source / topic_prompt:

  • If ${CLAUDE_PLUGIN_ROOT}/library/coding/<arg>.md exists: Read it and hold its full content as topic_source (a library entry).
  • Else if $CLAUDE_PROJECT_DIR/coding/imported/<arg>.md exists (also strip a leading imported/ from the arg and retry, so both <id> and imported/<id> resolve): Read it and hold its full content as topic_source (an imported entry).
  • Else if $ARGUMENTS is non-empty (a quoted free prompt — strip the surrounding quotes): treat it as a free-form problem statement — hold it verbatim as topic_prompt.
  • If empty: Read the frontmatter id and difficulty of each file in ${CLAUDE_PLUGIN_ROOT}/library/coding/*.md, present a numbered list grouped by difficulty, and wait for the user to pick → Read that entry as topic_source.

When topic_source is set, hold its ## Test cases JSON block (if present), its ## Follow-ups & variations, and its frontmatter patterns and signature for later steps. A library/imported entry grounds the interviewer's probes but is never read aloud verbatim.

Step 2 — Compute the session folder + seed the scratch file

Compute the session folder up front: $CLAUDE_PROJECT_DIR/coding/sessions/<YYYY-MM-DD-HHMM>-mock-coding/ where <YYYY-MM-DD-HHMM> comes from date +%Y-%m-%d-%H%M. Hold it as session_folder. Hold solution_file = <session_folder>/solution.py.

Write solution.py into the session folder, seeded as follows (Writing with the full absolute path creates intermediate dirs automatically — no mkdir needed):

  • topic_source with a ## Starter stub python block → write that block's body verbatim.
  • topic_source without a starter stub → synthesize from the frontmatter signature:
    from typing import List   # include only if a param/return type references List/Dict/Optional/etc.
    
    def <signature.name>(<param-name>: <param-type>, …) -> <signature.returns>:
        # your code here
        pass
    
  • topic_prompt (free-form, no signature) → a generic stub:
    def solve(*args):
        # your code here
        pass
    

Read the full file on GitHub · 149 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. 4d ago First seen · 149 lines · 0 tokens per session scan A 0211bb782b3e

Subscribe to this mod's changes

mock-coding is a command published in the GitHub repository kirilxd/swe-interview-coach (79 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,187 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.