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/junghwayang/oh-my-codex/deepsearchnpx skills add junghwaYang/oh-my-codex --skill deepsearchgit clone --depth 1 https://github.com/junghwaYang/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/junghwayang/oh-my-codex/deepsearch)<a href="https://agentmods.dev/skills/junghwayang/oh-my-codex/deepsearch"><img src="https://agentmods.dev/badge/skills/junghwayang/oh-my-codex/deepsearch.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.00498 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
deepsearch 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deepsearch Skill
Deep codebase exploration and understanding.
When to Use
- Understanding unfamiliar codebases
- Finding specific implementations
- Tracing data flow
- Mapping dependencies
- Onboarding to projects
When NOT to Use
- When you already know the location
- Simple file lookups
Search Capabilities
Structural Search
Find all:
- Components that use a specific hook
- Functions that call an API
- Classes that implement an interface
- Files that import a module
Semantic Search
Find code that:
- Handles authentication
- Processes payments
- Validates user input
- Manages state
Pattern Search
Find patterns:
- N+1 query potential
- Unused exports
- Circular dependencies
- Code duplication
Exploration Strategies
Top-Down
Entry point → Main modules → Sub-modules → Details
Bottom-Up
Specific function → Callers → Higher-level usage
Data Flow
Input → Transformations → Output
Dependency Graph
Module → Imports → Transitive dependencies
Output Format
## Codebase Analysis: {scope}
### Structure Overview
src/ ├── components/ # React components ├── hooks/ # Custom hooks ├── services/ # API services ├── utils/ # Utilities └── types/ # TypeScript types
### Key Files
| File | Purpose | Dependencies |
|------|---------|--------------|
| auth.ts | Authentication | api, storage |
| api.ts | HTTP client | axios |
### Data Flow
User Input → Validation → API Call → State Update → UI Render
### Findings
1. {finding 1}
2. {finding 2}
### Recommendations
- {recommendation}
Usage
deepsearch: how does authentication work in this codebase
deepsearch: find all places that handle payment processing
deepsearch: map the data flow for user registration
Tips
- Start broad, narrow down - Overview first, then details
- Follow the data - Trace from input to output
- Check tests - Tests reveal expected behavior
- Read types first - TypeScript types document structure
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 · 115 lines · 0 tokens per session scan A 1afdd79a0d77
deepsearch is a skill published in the GitHub repository junghwaYang/oh-my-codex (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 498 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-31.
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…