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 skills/haoruilee/oh-my-mcode/interviewnpx skills add haoruilee/oh-my-mcode --skill interviewgit clone --depth 1 https://github.com/haoruilee/oh-my-mcodeWhat 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.00094 | $0.00502 |
| Opus 5 | $0.00047 | $0.00251 |
| Sonnet 5 | $0.00019 | $0.00100 |
| Haiku 4.5 | $0.00009 | $0.00050 |
Grade A, and why
interview 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
Interview
TypeScript intake. Four short questions. Writes interview.md + interview.json with derived acceptance. Stops at PLAN_REVIEW. No builder. No Accepted.
中文名：交付访谈。
Inputs
- Goal. Optional constraints the user already stated.
- Workspace root.
- MCP first:
omm_interviewwhen present. Else CLI:oh-my-mcode interview "<goal>". - Non-interactive:
--answers answers.jsonor--constraint(repeatable).
Procedure
- Create or load the run. Do not start EXECUTE.
- Ask only: goal, constraints, acceptance, out of scope. Do not invent a long form.
- Persist interview artifacts via the harness / run store. Seed
tasks.jsonacceptance from the answers. - Stop at PLAN_REVIEW. Point the user at
max(ormax --interviewif they want the loop after intake).
Output contract
interview.mdandinterview.jsonon disk.- Phase
PLAN_REVIEW. Status is not Accepted. - No product edits.
Failure handling
- Non-TTY without answers/constraints: stop and ask for
--answersor--constraint. - User says "just do it": switch to the
maxskill.
Examples
User: interview this: fix the failing auth tests
Ask four questions (or load answers), write artifacts, stop.
User: max mode: fix the failing auth tests
Wrong skill. That is the full loop (max).
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 · 54 lines · 94 tokens per session scan A 241c861c0b43
interview is a skill published in the GitHub repository haoruilee/oh-my-mcode (51 stars, last pushed 4d ago), licensed MIT. It adds 94 tokens to every session and 502 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…