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/kirilxd/swe-interview-coach/mock-codinggit clone --depth 1 https://github.com/kirilxd/swe-interview-coachWrote 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/commands/kirilxd/swe-interview-coach/mock-coding)<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>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 | $0.00000 | $0.02187 |
| Opus 5 | $0.00000 | $0.01094 |
| Sonnet 5 | $0.00000 | $0.00437 |
| Haiku 4.5 | $0.00000 | $0.00219 |
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.
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>.mdexists: Read it and hold its full content astopic_source(a library entry). - Else if
$CLAUDE_PROJECT_DIR/coding/imported/<arg>.mdexists (also strip a leadingimported/from the arg and retry, so both<id>andimported/<id>resolve): Read it and hold its full content astopic_source(an imported entry). - Else if
$ARGUMENTSis non-empty (a quoted free prompt — strip the surrounding quotes): treat it as a free-form problem statement — hold it verbatim astopic_prompt. - If empty: Read the frontmatter
idanddifficultyof 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 astopic_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_sourcewith a## Starter stubpython block → write that block's body verbatim.topic_sourcewithout a starter stub → synthesize from the frontmattersignature: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 passtopic_prompt(free-form, no signature) → a generic stub:def solve(*args): # your code here pass
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.
- 4d ago First seen · 149 lines · 0 tokens per session scan A 0211bb782b3e
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.
Other commands, from other repositories
learn
Force claude-smart to extract learnings from this session now.
init
Install the formatters this repository needs, with every command visible before it runs.
brand-generate
Generate an on-brand document from a saved Brand Profile.
genshijin-compress
Markdown・テキストファイルを原始人形式へ安全圧縮.
save
Save this conversation as a new or existing reusable context.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.