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 rules/jkudjo/oh-my-cursor/deep-interviewgit clone --depth 1 https://github.com/Jkudjo/oh-my-cursorWhat 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.00011 | $0.00992 |
| Opus 5 | $0.00005 | $0.00496 |
| Sonnet 5 | $0.00002 | $0.00198 |
| Haiku 4.5 | $0.00001 | $0.00099 |
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 yesterday.
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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@deep-interview
Trigger: When scope, intent, or requirements are unclear. Use before @ralplan or @ralph on any non-trivial task.
Depth Profiles
| Flag | Threshold | Max Rounds | Use when |
|---|---|---|---|
--quick |
≤ 0.30 | 5 | Minor changes, mostly clear intent |
--standard (default) |
≤ 0.20 | 12 | Features, refactors |
--deep |
≤ 0.15 | 20 | Architecture changes, large scope |
Protocol
Phase 0 — Preflight
- Call
start_modewith mode=deep-interviewand the raw task. - Classify: greenfield (new) vs brownfield (existing codebase). For brownfield, read relevant files first — never ask the user for facts you can discover.
- Call
save_artifacttype=context, slug=deep-interview-{task-slug}, with initial snapshot:Task: ... Hypothesis: why the user likely wants this Known facts: ... Unknowns: ... Decision boundaries: ...
Phase 1 — Interview Loop
Repeat until ambiguity ≤ threshold OR max rounds reached:
-
Ask ONE question targeting the weakest clarity dimension.
- Never batch questions. One question per turn.
- Priority order: Intent → Outcome → Scope → Non-goals → Decision Boundaries → Constraints → Success Criteria
- For brownfield: use evidence-backed questions ("I see X in Y — should changes follow that pattern?")
- After each answer: probe assumptions, not just facts. Ask for evidence, counterexamples, or tradeoffs before moving to the next dimension.
-
Score ambiguity after each answer (0.0 = fully clear, 1.0 = fully unclear):
Greenfield:
ambiguity = 1 - (intent×0.30 + outcome×0.25 + scope×0.20 + constraints×0.15 + success×0.10)Brownfield:
ambiguity = 1 - (intent×0.25 + outcome×0.20 + scope×0.20 + constraints×0.15 + success×0.10 + context×0.10) -
Show progress each round:
Round N | Ambiguity: 0.XX → 0.XX | Focus: {dimension} -
Call
update_mode_statewithphase={dimension}anditeration=N.
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.
- yesterday First seen · 99 lines · 11 tokens per session scan A 66cde96adc9e
deep-interview is a cursor rule published in the GitHub repository Jkudjo/oh-my-cursor (1 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 992 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
implementation-workflow
Required plan-first workflow for any implementation request (steps 1–5).
memory-bank
You are an expert software engineer with a unique characteristic: your memory resets completely between sessions. This isn't a limitation - it's what drives you to maintain perfect documentation. At the beginning of each dialogue, you rely ENTIRELY on your Memory Bank to understand the project and continue work…
general
You are running in Cursor IDE. The tools of the MCP server that you are developing are connected to this IDE. When you've modified the code and want to use updated functionality, you must prompt the user to reload the server first.
create-rule-agent
This rule is responsible for creating and updating Cursor rules. Cursor rules govern the structure, hierarchy, style and organization of code in a project. This rule should be invoked in Agent mode when: 1. a user wants to create a new cursor rule, 2. a user wants to update or change an existing rule, 3. user wants…
cloudflare-workers-hono-auto
Cloudflare Workers with Hono framework development standards and best practices.