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 IvanLutsenko/awac-ai-agent-plugins/plugin install plugin-cross-portWrote 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/ivanlutsenko/awac-ai-agent-plugins/codex-to-cc)<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/codex-to-cc"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/codex-to-cc/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/skills/ivanlutsenko/awac-ai-agent-plugins/codex-to-cc"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/codex-to-cc.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.00050 | $0.01503 |
| Opus 5.5 | $0.00020 | $0.00601 |
| Sonnet 5.5 | $0.00010 | $0.00301 |
| Haiku 4.5 | $0.00005 | $0.00150 |
Grade A, and why
codex-to-cc 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.
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Convert Codex Plugin → Claude Code
Convert a single plugin from Codex format to Claude Code-compatible format.
When to activate
- User says "convert X from Codex to CC", "add Claude Code support for X", "reverse-port X"
- User provides a Codex plugin path and asks for CC compatibility
- Round-trip recovery: CC plugin was converted to Codex, now needs CC files restored
Inputs
- Plugin path — relative to repo root, e.g.
plugins/my-codex-plugin - Repo root — directory containing
.agents/plugins/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):
<plugin-path>/.codex-plugin/plugin.json— required<plugin-path>/skills/directory listing — list all SKILL.md files<plugin-path>/.mcp.json— optional<plugin-path>/README.md— optional<plugin-path>/.plugin-cross-port.json— optional (check source_of_truth)
If .codex-plugin/plugin.json is missing, stop and report: "Not a Codex plugin: no .codex-plugin/plugin.json found."
If .plugin-cross-port.json exists with source_of_truth: claude-code, warn:
"This plugin was originally created in Claude Code. Reverse conversion may produce redundant files. Proceed?"
Step 2 — Check for existing CC manifest
If <plugin-path>/.claude-plugin/plugin.json already exists, read it. Ask:
"
.claude-plugin/plugin.jsonalready exists. Overwrite or merge?"
Step 3 — Generate .claude-plugin/plugin.json
Build the CC manifest from the Codex manifest:
{
"name": "<same as Codex name>",
"description": "<same description>",
"version": "<same version>",
"author": {
"name": "<author.name>",
"email": "",
"url": ""
},
"keywords": ["<interface.category>", "codex", "cross-platform"],
"license": "MIT",
"skills": [
"./skills/<name>/SKILL.md"
// list all SKILL.md files from skills/
]
}
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 · 186 lines · 50 tokens per session scan A e3cfd43ad6b7
codex-to-cc is a skill published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (3 stars, last pushed 5d ago), licensed MIT. It adds 50 tokens to every session and 1,503 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.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…