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/mcp-setupnpx skills add junghwaYang/oh-my-codex --skill mcp-setupgit 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/mcp-setup)<a href="https://agentmods.dev/skills/junghwayang/oh-my-codex/mcp-setup"><img src="https://agentmods.dev/badge/skills/junghwayang/oh-my-codex/mcp-setup.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.00612 |
| Opus 5 | $0.00000 | $0.00306 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade B, and why
mcp-setup scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
### ~/.codex/config.toml How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Setup Skill
Configure Model Context Protocol servers.
What is MCP?
MCP (Model Context Protocol) allows Codex to connect to external tools and data sources:
- File systems
- Databases
- APIs
- Custom tools
Available Servers
Core Servers
| Server | Purpose | Install |
|---|---|---|
| filesystem | File operations | @anthropic/mcp-server-filesystem |
| github | GitHub API | @anthropic/mcp-server-github |
| postgres | PostgreSQL | @anthropic/mcp-server-postgres |
| sqlite | SQLite | @anthropic/mcp-server-sqlite |
Extended Servers
| Server | Purpose | Install |
|---|---|---|
| brave-search | Web search | @anthropic/mcp-server-brave-search |
| memory | Persistent memory | @anthropic/mcp-server-memory |
| puppeteer | Browser automation | @anthropic/mcp-server-puppeteer |
| slack | Slack integration | @anthropic/mcp-server-slack |
Configuration
~/.codex/config.toml
[mcp.filesystem]
command = "npx"
args = ["-y", "@anthropic/mcp-server-filesystem", "/path/to/allowed"]
[mcp.github]
command = "npx"
args = ["-y", "@anthropic/mcp-server-github"]
env = { GITHUB_TOKEN = "ghp_xxx" }
[mcp.postgres]
command = "npx"
args = ["-y", "@anthropic/mcp-server-postgres", "postgresql://user:pass@localhost/db"]
[mcp.brave]
command = "npx"
args = ["-y", "@anthropic/mcp-server-brave-search"]
env = { BRAVE_API_KEY = "xxx" }
Setup Commands
# Test MCP server
npx -y @anthropic/mcp-server-filesystem /tmp
# Verify configuration
omx --status
Usage
mcp-setup: configure GitHub integration
mcp-setup: add PostgreSQL database connection
mcp-setup: enable web search with Brave
Security Notes
- Limit filesystem access - Only allow necessary directories
- Use environment variables - Don't hardcode secrets
- Rotate tokens - Regular credential rotation
- Audit access - Review what MCP servers can do
Troubleshooting
"MCP server not found"
# Install the server
npm install -g @anthropic/mcp-server-github
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 · 103 lines · 0 tokens per session scan B 730ba66017eb
mcp-setup 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 612 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). 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…