codex-research

codex-research is a skill for Claude Code from signalcompose/claude-tools. It costs 37 tokens per session (600 once invoked), scanned A, original, MIT.

A skill that uses the OpenAI Codex command-line tool to research technical topics, look up documentation, explain concepts, and review code.

In plain words
What is it for?
Use it for technical questions, documentation lookup, concept explanations, and reviews of files, directories, or uncommitted changes. Codex CLI and authentication must be set up first.
Why use it?
It gives you a separate command-line review or research step when you need documentation, best-practice guidance, or another analysis of code.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: agent in frontmatter; runs codex exec; mentions Codex.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the ask-codex plugin — 1 skill, 2 commands shipped together

Good fit Use it for technical questions, documentation lookup, concept explanations, and reviews of files, directories, or uncommitted changes. Codex CLI and authentication must be set up first.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add signalcompose/claude-tools
Claude Code
/plugin install ask-codex

Made for: Claude Code.

Or install ask-codex, the plugin that ships this one along with the rest of its 1 skill, 2 commands.

Wrote 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.

agentmods badge for codex-research

README.md
[![agentmods](https://agentmods.dev/badge/skills/signalcompose/claude-tools/codex-research/github.svg)](https://agentmods.dev/skills/signalcompose/claude-tools/codex-research)
Your own site
<a href="https://agentmods.dev/skills/signalcompose/claude-tools/codex-research"><img src="https://agentmods.dev/badge/skills/signalcompose/claude-tools/codex-research/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for codex-research

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 600 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.00600
Opus 5.5 $0.00015 $0.00240
Sonnet 5.5 $0.00007 $0.00120
Haiku 4.5 $0.00004 $0.00060

Measured 1mo ago against content hash a5f43a7f72a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

plugins/ask-codex/skills/codex-research/SKILL.md · 87 lines

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 codex to complete OAuth authentication, OR
    • Set OPENAI_API_KEY environment variable

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 (uses codex review <file>)
  • <directory> - Review directory (uses codex 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

  1. First, verify Codex CLI is available using check-codex.sh
  2. For research tasks, use codex-exec.sh with the research prompt
  3. For code review, use codex-review.sh with 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

Read the full file on GitHub · 87 lines

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.

  1. 1mo ago First seen · 87 lines · 37 tokens per session scan A a5f43a7f72a8

Subscribe to this mod's changes

codex-research is a skill published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 600 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens