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/signalcompose/claude-tools/codex-researchnpx skills add signalcompose/claude-tools --skill codex-researchgit clone --depth 1 https://github.com/signalcompose/claude-toolsWrote 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/signalcompose/claude-tools/codex-research)<a href="https://agentmods.dev/skills/signalcompose/claude-tools/codex-research"><img src="https://agentmods.dev/badge/skills/signalcompose/claude-tools/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.00037 | $0.00600 |
| Opus 5 | $0.00018 | $0.00300 |
| Sonnet 5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
codex-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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Research Skill
This skill provides integration with OpenAI Codex CLI for research and code review tasks.
Prerequisites
- Codex CLI installed:
npm install -g @openai/codex - Authentication (one of):
- Run
codexto complete OAuth authentication, OR - Set
OPENAI_API_KEYenvironment variable
- Run
Available Scripts
All scripts are located in ${CLAUDE_PLUGIN_ROOT}/scripts/.
1. Check Installation
${CLAUDE_PLUGIN_ROOT}/scripts/check-codex.sh
Verifies Codex CLI is installed and authentication is configured (OAuth or API key).
2. Research Mode (codex exec)
${CLAUDE_PLUGIN_ROOT}/scripts/codex-exec.sh "your research question"
Use for:
- Technical research questions
- Documentation lookup
- Concept explanations
- Best practices inquiry
Example:
${CLAUDE_PLUGIN_ROOT}/scripts/codex-exec.sh "What is dependency injection and when should I use it?"
3. Code Review Mode
${CLAUDE_PLUGIN_ROOT}/scripts/codex-review.sh <target>
Options:
--staged- Review all uncommitted changes (staged + unstaged)<file>- Review specific file (usescodex review <file>)<directory>- Review directory (usescodex review <dir>)
Important: --staged uses codex exec review uncommitted which reviews all uncommitted changes, not just staged files. To review only specific files, use the file/directory target.
Examples:
${CLAUDE_PLUGIN_ROOT}/scripts/codex-review.sh --staged
${CLAUDE_PLUGIN_ROOT}/scripts/codex-review.sh src/main.ts
${CLAUDE_PLUGIN_ROOT}/scripts/codex-review.sh ./lib
Workflow
- First, verify Codex CLI is available using
check-codex.sh - For research tasks, use
codex-exec.shwith the research prompt - For code review, use
codex-review.shwith the target
Error Handling
- Timeout: Commands timeout after 120 seconds
- Not installed: Provides installation instructions
- Not authenticated: Prompts to complete OAuth or set OPENAI_API_KEY
Notes
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 · 87 lines · 37 tokens per session scan A a5f43a7f72a8
codex-research is a skill published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 8d ago), licensed MIT. It adds 37 tokens to every session and 600 once invoked, about $0.0002 per session on Opus 5. 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…