# OpenCodex Proxy Operations

Operates the opencodex proxy: accounts, providers, models, routing, and usage.

- Repository: https://github.com/lidge-jun/opencodex (18143 stars)
- Category: DevOps
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add lidge-jun/opencodex --skill ocx -g -a claude-code -y`
Codex: `npx skills add lidge-jun/opencodex --skill ocx -g -a codex -y`
Cursor: `npx skills add lidge-jun/opencodex --skill ocx -g -a cursor -y`
Gemini CLI: `npx skills add lidge-jun/opencodex --skill ocx -g -a gemini-cli -y`

## Description

Operate opencodex (`ocx`): discover CLI tasks offline, inspect local configuration, and manage a running proxy’s account pool, providers, models, routing, usage report, and management API. Use for proxy operation rather than editing the opencodex codebase.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Operating `ocx`

`ocx` supports local configuration and named live management workflows. Coverage is
per task: provider edits, account selection, model visibility, routing reads, client
integration controls and diagnostics have different transports and limits. A shared
API prefix does not prove that every dashboard action has a CLI equivalent.

This skill is for **operating** a proxy. `AGENTS_INSTALL.md` covers installation
and operating consent; the repository `AGENTS.md` covers code changes.

## Find the task offline

Start at the smallest useful level; no running proxy is needed for help:

```bash
ocx help                         # compact root
ocx help models                  # family and declared children
ocx help models preset show      # exact leaf, when declared
ocx help --all                   # full top-level reference, when needed
```

Then read only the matching [task chapter](references/01_management_surface.md).
For example, use [providers/models](references/01_surface_providers-models.md)
for catalog work or [Lab](references/01_surface_lab.md) for local evidence.
Use `ocx help <family> <leaf>` or appended `--help`, not a trailing bare `help`
after nested operands. Missing detail can fall back to family help; it is not
proof that a runtime operation is absent.

For a route you already know, an optional lookup is:

```bash
ocx capabilities --route '/api/providers/{provider}/model-costs' --json
```

This matches the **declared path template**, not a concrete provider URL or HTTP
method. Exit 4 means no declaration matched. Full `ocx capabilities --json` and
`--mutating-only --json` are useful for broad inventories, not mandatory preflight.
Declarations describe the installed CLI; actual handlers remain the grammar authority.

## Choose a workflow

The rest: https://github.com/lidge-jun/opencodex/blob/HEAD/skills/ocx/SKILL.md