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 skills add scalarian/oh-my-codex --skill deep-interviewgit clone --depth 1 https://github.com/scalarian/oh-my-codexWrote 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/skills/scalarian/oh-my-codex/deep-interview)<a href="https://agentmods.dev/skills/scalarian/oh-my-codex/deep-interview"><img src="https://agentmods.dev/badge/skills/scalarian/oh-my-codex/deep-interview/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/scalarian/oh-my-codex/deep-interview"><img src="https://agentmods.dev/badge/skills/scalarian/oh-my-codex/deep-interview.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00022 | $0.00485 |
| Opus 5.5 | $0.00009 | $0.00194 |
| Sonnet 5.5 | $0.00004 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
deep-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 1mo 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Interview
Purpose
Use $deep-interview to turn a fuzzy request into an execution-ready spec. This is not generic brainstorming. It is a focused clarification loop that removes ambiguity before planning or coding.
Use When
- the request describes outcomes, not behavior
- the user is still discovering what they want
- scope, non-goals, or decision boundaries are unclear
- a wrong assumption would create expensive rework
Do Not Use When
- the request already names files, symbols, and acceptance criteria
- the user explicitly wants immediate execution and the risk is low
- the only missing work is architectural decomposition, not intent clarity
Execution Policy
- Ask one question at a time.
- Ask only the highest-leverage unresolved question.
- Use repo facts before asking the user about codebase internals.
- Force clarity on non-goals and decision boundaries before handing off.
- Keep the interview moving toward a written artifact, not an endless conversation.
Question Order
- Why does this need to exist?
- What should be true when it is done?
- How far should it go?
- What should explicitly stay out?
- What may OMX decide without checking again?
- What constraints or preferences are hard?
Workflow
- Read current
.omx/artifacts and inspect the repo if this is brownfield work. - Capture the current hypothesis in
.omx/plans/<phase>-requirements.md. - Run a one-question loop until these are explicit:
- goal
- in-scope
- out-of-scope
- acceptance criteria
- decision boundaries
- Update:
.omx/plans/<phase>-requirements.md.omx/research/summary.md.omx/state/planning-state.json
- Hand off to
$planwhen the spec is concrete.
Output Standard
The finished interview should leave behind:
- clear goal
- explicit non-goals
- decision boundaries
- testable acceptance criteria
- constraints that downstream execution must honor
Stop Conditions
Do not hand off while either of these is missing:
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.
- 1mo ago First seen · 74 lines · 22 tokens per session scan A b13c5b95713b
deep-interview is a skill published in the GitHub repository scalarian/oh-my-codex (73 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 485 once invoked, about $0.0001 per session on Opus 5.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
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
refocusing
Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.
printing-press-import
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a…
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.