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/security-reviewnpx skills add junghwaYang/oh-my-codex --skill security-reviewgit 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/security-review)<a href="https://agentmods.dev/skills/junghwayang/oh-my-codex/security-review"><img src="https://agentmods.dev/badge/skills/junghwayang/oh-my-codex/security-review.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.1 | $0.00000 | $0.00721 |
| Opus 5 | $0.00000 | $0.00360 |
| Sonnet 5 | $0.00000 | $0.00144 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
security-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 6d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review Skill
Focused security audit for code and architecture.
When to Use
- Before deploying to production
- After adding authentication/authorization
- When handling sensitive data
- Regular security audits
- Compliance requirements
OWASP Top 10 Checklist
1. Broken Access Control
□ Authentication on all protected routes
□ Authorization checks for resources
□ No direct object references exposed
□ CORS properly configured
□ JWT validation complete
2. Cryptographic Failures
□ Sensitive data encrypted at rest
□ TLS for data in transit
□ Strong hashing for passwords (bcrypt, argon2)
□ No hardcoded secrets
□ Proper key management
3. Injection
□ Parameterized queries (no string concat)
□ Input validation
□ Output encoding
□ ORM used correctly
□ Command injection prevention
4. Insecure Design
□ Threat modeling done
□ Security requirements defined
□ Secure defaults
□ Defense in depth
□ Least privilege principle
5. Security Misconfiguration
□ Default credentials changed
□ Unnecessary features disabled
□ Error messages don't leak info
□ Security headers set
□ Dependencies up to date
6. Vulnerable Components
□ Dependencies scanned (npm audit, etc.)
□ Known vulnerabilities addressed
□ Components from trusted sources
□ Unused dependencies removed
7. Auth Failures
□ Strong password requirements
□ Rate limiting on auth endpoints
□ Session management secure
□ Multi-factor available
□ Secure password reset
8. Data Integrity Failures
□ Integrity verification for data
□ Signed updates/packages
□ CI/CD pipeline secured
□ Serialization safe
9. Logging Failures
□ Security events logged
□ Logs don't contain secrets
□ Log injection prevented
□ Monitoring/alerting set up
10. SSRF
□ URL validation
□ Allowlist for external calls
□ Network segmentation
□ Metadata endpoint blocked
Quick Checks
Secrets
# Look for hardcoded secrets
grep -r "password\|secret\|api_key\|token" --include="*.ts" --include="*.js"
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.
- 6d ago First seen · 160 lines · 0 tokens per session scan A 53f378292c03
security-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 721 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…
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…
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…
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…