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/jmstar85/oh-my-githubcopilot/deep-divenpx skills add jmstar85/oh-my-githubcopilot --skill deep-divegit clone --depth 1 https://github.com/jmstar85/oh-my-githubcopilotWrote 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/jmstar85/oh-my-githubcopilot/deep-dive)<a href="https://agentmods.dev/skills/jmstar85/oh-my-githubcopilot/deep-dive"><img src="https://agentmods.dev/badge/skills/jmstar85/oh-my-githubcopilot/deep-dive.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.00040 | $0.00507 |
| Opus 5 | $0.00020 | $0.00253 |
| Sonnet 5 | $0.00008 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
deep-dive 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 5d 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.
This is a copy
94% identical to deep-dive — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Deep Dive
Orchestrates a 2-stage pipeline: first investigate WHY something happened (trace), then define WHAT to do about it (deep-interview). Trace findings feed into the interview via 3-point injection.
Pipeline
deep-dive → ralplan (consensus refinement) → omg-autopilot (execution)
When to Use
- User has a problem but doesn't know the root cause
- Bug investigation: "Something broke and I need to figure out why"
- Feature exploration: "I want to improve X but first need to understand it"
When NOT to Use
- Already know the root cause → use
/deep-interview - Clear specific request → execute directly
- Investigation only, no requirements → use
/trace
Phases
Phase 1: Initialize
- Parse problem, detect brownfield/greenfield
- Generate 3 trace lane hypotheses (code-path, config/env, measurement/artifact)
Phase 2: Lane Confirmation
Present hypotheses to user for confirmation (1 round).
Phase 3: Trace Execution
Run 3 parallel tracer lanes using @tracer agents:
- Each lane: evidence for, evidence against, critical unknown, discriminating probe
- Rebuttal round between top hypotheses
- Convergence detection
- Save to
.omg/specs/deep-dive-trace-{slug}.md
Phase 4: Interview with Trace Injection
Follow deep-interview protocol with 3 overrides:
- initial_idea enrichment: Include trace's most likely explanation
- codebase_context replacement: Use trace synthesis (skip re-exploration)
- question queue injection: Per-lane critical unknowns become first questions
Low-confidence trace: don't inject uncertain conclusion, use ALL unknowns as questions.
Phase 5: Execution Bridge
Same options as deep-interview: ralplan → omg-autopilot (recommended), omg-autopilot, ralph, team, or refine further.
Output
Spec saved to .omg/specs/deep-dive-{slug}.md with additional "Trace Findings" section.
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.
- 5d ago First seen · 55 lines · 40 tokens per session scan A dd58bf0db3cc
deep-dive is a skill published in the GitHub repository jmstar85/oh-my-githubcopilot (153 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 507 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to deep-dive, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…