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/researchnpx skills add junghwaYang/oh-my-codex --skill researchgit 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/research)<a href="https://agentmods.dev/skills/junghwayang/oh-my-codex/research"><img src="https://agentmods.dev/badge/skills/junghwayang/oh-my-codex/research.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.00542 |
| Opus 5 | $0.00000 | $0.00271 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
research 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 4d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Skill
Deep research and information gathering.
When to Use
- Evaluating technology options
- Understanding new APIs/libraries
- Investigating best practices
- Comparing solutions
- Learning new concepts
When NOT to Use
- When answer is already known
- Simple documentation lookups
- Time-critical tasks
Research Process
1. Define Question
What exactly do we need to know?
- Specific question
- Success criteria
- Scope boundaries
2. Gather Sources
Primary sources:
- Official documentation
- GitHub repos
- Academic papers
- RFC specifications
Secondary sources:
- Blog posts
- Stack Overflow
- Community forums
- Video tutorials
3. Analyze & Compare
For each option:
- Pros and cons
- Use cases
- Limitations
- Community support
- Maintenance status
4. Synthesize
- Summary of findings
- Recommendation
- Supporting evidence
- Caveats/risks
Research Templates
Technology Comparison
## {Topic} Comparison
### Options Evaluated
1. {Option A}
2. {Option B}
3. {Option C}
### Comparison Matrix
| Criteria | Option A | Option B | Option C |
|----------|----------|----------|----------|
| Performance | ⭐⭐⭐ | ⭐⭐ | ⭐⭐⭐⭐ |
| Ease of Use | ⭐⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐ |
| Community | ⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ | ⭐⭐ |
| Documentation | ⭐⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐⭐ |
### Recommendation
{Option X} because {reasons}
### Risks
- {potential issues}
Best Practice Research
## Best Practices: {Topic}
### Industry Standards
- {standard 1}
- {standard 2}
### Common Patterns
1. {pattern} - {when to use}
2. {pattern} - {when to use}
### Anti-patterns to Avoid
- {anti-pattern} - {why it's bad}
### Sources
- {source 1}
- {source 2}
Usage
research: compare React state management solutions
research: best practices for API rate limiting
research: evaluate database options for time-series data
Output Guidelines
- Be specific - Cite sources, version numbers
- Be objective - Present tradeoffs fairly
- Be actionable - End with clear recommendation
- Be current - Note when info might be outdated
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.
- 4d ago First seen · 123 lines · 0 tokens per session scan A 27c06c58bc95
research 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 542 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.
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…