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.
/plugin marketplace add DropFan/claude-code-plugins/plugin install codex-bridgeWrote 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/commands/dropfan/claude-code-plugins/codex)<a href="https://agentmods.dev/commands/dropfan/claude-code-plugins/codex"><img src="https://agentmods.dev/badge/commands/dropfan/claude-code-plugins/codex/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.
<a href="https://agentmods.dev/commands/dropfan/claude-code-plugins/codex"><img src="https://agentmods.dev/badge/commands/dropfan/claude-code-plugins/codex.svg" alt="Reviewed on agentmods" width="80" 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.00013 | $0.01366 |
| Opus 5.5 | $0.00005 | $0.00546 |
| Sonnet 5.5 | $0.00003 | $0.00273 |
| Haiku 4.5 | $0.00001 | $0.00137 |
Grade B, and why
codex 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep '^model' ~/.codex/config.toml 2>/dev/null | head -1 | sed 's/.*= *"\?\([^"]*\)"\?/\1/' How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Working directory: !
pwd - Plugin root: ${CLAUDE_PLUGIN_ROOT}
- Codex installed: !
codex --version 2>&1 || echo "NOT INSTALLED"
Task
Act as an orchestration layer: understand the user's intent, gather relevant context, compose a self-contained prompt, send it to Codex, and analyze the result.
User request: $ARGUMENTS
Step 1: Pre-checks
- If Codex is not installed (version shows "NOT INSTALLED"), tell the user: "Codex CLI is not installed. Run
npm install -g @openai/codexto install, thencodex loginto configure your API key." Stop here. - If $ARGUMENTS is blank, ask the user what they want Codex to do. Provide 2-3 example prompts based on the current project context (e.g., files recently discussed). Do not proceed with an empty prompt.
Step 2: Understand Intent
Analyze $ARGUMENTS and resolve any ambiguous or contextual references:
- Resolve vague references — "that function", "the file we discussed", "this bug" → look back at conversation history to identify specific file paths, function names, or code snippets.
- Identify the task type — analysis, verification, comparison, documentation review, etc.
- Determine scope — which files, directories, or code regions are relevant.
If a reference cannot be resolved from conversation context, ask the user for clarification rather than guessing.
Step 3: Collect Context
Based on the resolved intent, gather only the directly relevant context. Use these tools as needed:
| Need | Action |
|---|---|
| File content discussed in conversation | Read key files or snippets (keep to relevant sections) |
| Recent changes | git diff --stat, git diff <file> for specific files |
| Project structure | ls relevant directories |
| Git state | git status --short, git log --oneline -5 |
| Current branch | git branch --show-current |
Limits: Collect only what Codex needs to do the job. Total context should not exceed ~200 lines. Prefer targeted snippets over full file dumps.
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.
- 1mo ago First seen · 119 lines · 13 tokens per session scan B 052e4426bd00
codex is a command published in the GitHub repository DropFan/claude-code-plugins (8 stars, last pushed 25d ago), licensed MIT. It adds 13 tokens to every session and 1,366 once invoked, about $0.0001 per session on Opus 5.5. 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 commands, from other repositories
prompt
System instructions for writing effective prompts. Apply when generating commands, skills, agents, or any LLM instructions.
full
Run the full hope pipeline — intent, shape, target, freeze as needed — then execute.
status
Show tlive daemon, channel, and Codex companion status.
csv-to-numbers
Convert a CSV into a formatted Numbers workbook.
close
Close out a Linear issue — move to Done, add a closing comment, and clean up the local branch/worktree.
prompt
Convert a rough ask into a structured XML-tagged prompt using the factory-prompting vocabulary.