cc-to-codex

cc-to-codex is a skill for Claude Code from IvanLutsenko/awac-ai-agent-plugins. It costs 39 tokens per session (1,845 once invoked), scanned A, original, MIT.

A skill that converts a Claude Code plugin into a format supported by Codex. It reads the plugin's configuration and available skills, commands, and agents as part of the conversion.

In plain words
What is it for?
Use it to convert or port a plugin, or to add Codex support to an existing Claude Code plugin.
Why use it?
It avoids manually restructuring a Claude Code plugin when you need Codex support.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions .claude-plugin; mentions Claude Code; 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 plugin-cross-port plugin — 4 skills, 1 command shipped together

Good fit Use it to convert or port a plugin, or to add Codex support to an existing Claude Code plugin.

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 IvanLutsenko/awac-ai-agent-plugins
Claude Code
/plugin install plugin-cross-port

Made for: Claude Code.

Or install plugin-cross-port, the plugin that ships this one along with the rest of its 4 skills, 1 command.

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 cc-to-codex

README.md
[![agentmods](https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/cc-to-codex/github.svg)](https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/cc-to-codex)
Your own site
<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/cc-to-codex"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/cc-to-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.

agentmods 80×15 button for cc-to-codex

Your own site · 80×15
<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/cc-to-codex"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/cc-to-codex.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,845 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.00039 $0.01845
Opus 5.5 $0.00016 $0.00738
Sonnet 5.5 $0.00008 $0.00369
Haiku 4.5 $0.00004 $0.00185

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

Security

Grade A, and why

cc-to-codex 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/plugin-cross-port/skills/cc-to-codex/SKILL.md · 227 lines

How it starts

The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Convert Claude Code Plugin → Codex

Convert a single plugin from Claude Code format to Codex-compatible format.

When to activate

  • User says "convert X to Codex", "port X to Codex", "add Codex support for X"
  • User provides a path like plugins/obsidian-tracker or just a plugin name

Inputs

  • Plugin path — relative to repo root, e.g. plugins/obsidian-tracker
  • Repo root — directory containing .claude-plugin/marketplace.json (default: detect from cwd)

Workflow

Phase 0: Vendor external plugins

When the plugin lives outside this repository, copy it into plugins_dir before conversion. Review license and attribution, resolve name collisions, discard stale foreign generated artifacts after review, and explicitly choose the source of truth when attaching. Deterministic scripts never copy files between repositories.

Step 1 — Read source

Read the following files from the target plugin (skip if absent):

  1. <plugin-path>/.claude-plugin/plugin.json — required
  2. <plugin-path>/.mcp.json — optional
  3. <plugin-path>/skills/ directory listing — optional
  4. <plugin-path>/commands/ directory listing — optional
  5. <plugin-path>/agents/ directory listing — optional
  6. <plugin-path>/README.md — optional

If .claude-plugin/plugin.json is missing, stop and report: "Not a Claude Code plugin: no .claude-plugin/plugin.json found."

Step 2 — Check for existing Codex manifest

If <plugin-path>/.codex-plugin/plugin.json already exists, read it and note what's already generated. Ask the user:

".codex-plugin/plugin.json already exists. Overwrite or merge?"

Step 3 — Generate .codex-plugin/plugin.json

Build the Codex manifest from the source Claude manifest:

{
  "name": "<same as CC name>",
  "version": "<same version>",
  "description": "<same description>",
  "author": {
    "name": "<author.name from CC>"
  },
  "skills": "./skills/",
  "interface": {
    "displayName": "<Title Case of plugin name>",
    "shortDescription": "<first sentence of description, max 80 chars>",
    "developerName": "<author.name>",
    "category": "Development",
    "capabilities": ["Read", "Write"]
  }
}

Read the full file on GitHub · 227 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 · 227 lines · 39 tokens per session scan A ef59b6e3e59c

Subscribe to this mod's changes

cc-to-codex is a skill published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (3 stars, last pushed 5d ago), licensed MIT. It adds 39 tokens to every session and 1,845 once invoked, about $0.0002 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-09-05.

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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 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