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/code-reviewnpx skills add junghwaYang/oh-my-codex --skill code-reviewgit clone --depth 1 https://github.com/junghwaYang/oh-my-codexWhat 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.00566 |
| Opus 5 | $0.00000 | $0.00283 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
code-review 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 2d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Skill
Comprehensive code review with security, performance, and quality checks.
When to Use
- Before merging PRs
- After completing features
- Security audits
- Performance optimization
- Code quality improvement
Review Categories
| Category | Prefix | Priority | Focus |
|---|---|---|---|
| Security | SEC- | CRITICAL | Vulnerabilities, auth, data exposure |
| Performance | PERF- | HIGH | Speed, memory, scalability |
| Correctness | BUG- | HIGH | Logic errors, edge cases |
| Maintainability | MAINT- | MEDIUM | Readability, complexity |
| Style | STYLE- | LOW | Formatting, naming |
Review Process
1. Security Review (SEC-)
□ No hardcoded secrets
□ Input validation present
□ SQL injection prevention
□ XSS protection
□ CSRF protection
□ Authentication checks
□ Authorization checks
□ Sensitive data handling
□ Secure dependencies
2. Performance Review (PERF-)
□ No N+1 queries
□ Proper indexing
□ Efficient algorithms (O notation)
□ Memory management
□ Caching strategy
□ Bundle size (frontend)
□ Lazy loading
□ Database query optimization
3. Correctness Review (BUG-)
□ Logic is sound
□ Edge cases handled
□ Null/undefined checks
□ Error handling
□ Race conditions
□ State management
□ Type safety
4. Maintainability Review (MAINT-)
□ Single responsibility
□ DRY principle
□ Clear naming
□ Appropriate comments
□ Reasonable complexity
□ Test coverage
□ Documentation
Output Format
## Code Review: {scope}
### Summary
{1-2 sentence assessment}
### Critical Issues
- **SEC-001**: {issue}
- File: {path}:{line}
- Risk: {description}
- Fix: {suggestion}
### High Priority
- **PERF-001**: {issue}
- File: {path}:{line}
- Impact: {description}
- Fix: {suggestion}
### Medium Priority
- **MAINT-001**: {issue}
- Suggestion: {improvement}
### Low Priority
- **STYLE-001**: {issue}
### Positive Notes
- {good practice observed}
### Verdict
[ ] ✅ Approve
[ ] ⚠️ Approve with comments
[ ] ❌ Request changes
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.
- 2d ago First seen · 120 lines · 0 tokens per session scan A dc5104c90040
code-review 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 566 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…