codex — servidor proxy multi-tenant qcc_plus, community, servidor proxy multi-tenant, ide skills, conmutación automática, administración web, Docker, Golang, TypeScript, herramienta Codex, Claude Code

v1.0.0

Acerca de este Skill

Perfecto para agentes de codificación que necesitan automatización avanzada y optimización del flujo de trabajo con Claude Code y el modelo gpt-5.1-codex-max Un servidor proxy multi-tenant para Claude Code que permite la conmutación automática y la administración web

Características

Servidor proxy multi-tenant
Conmutación automática
Administración web
Compatibilidad con Docker y Golang
Interfaz de usuario basada en React
Soporte para TypeScript

# Core Topics

yxhpy yxhpy
[41]
[14]
Updated: 3/16/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
8/11
Quality Score
34
Canonical Locale
en
Detected Body Locale
en

Perfecto para agentes de codificación que necesitan automatización avanzada y optimización del flujo de trabajo con Claude Code y el modelo gpt-5.1-codex-max Un servidor proxy multi-tenant para Claude Code que permite la conmutación automática y la administración web

¿Por qué usar esta habilidad?

Habilita a los agentes a automatizar tareas de codificación con un gran esfuerzo de razonamiento utilizando el modelo gpt-5.1-codex-max, lo que permite el soporte multi-tenant, el failover automático y las interfaces de administración web a través de Codex, un servidor proxy CLI de Claude Code, aprovechando los protocolos CLI y el razonamiento de alto nivel para la automatización del flujo de trabajo optimizada

Mejor para

Perfecto para agentes de codificación que necesitan automatización avanzada y optimización del flujo de trabajo con Claude Code y el modelo gpt-5.1-codex-max

Casos de uso accionables for codex

Automatizar tareas de codificación con el modelo gpt-5.1-codex-max
Optimizar la automatización del flujo de trabajo para los desarrolladores
Habilitar el soporte multi-tenant y el failover automático para tareas de codificación

! Seguridad y limitaciones

  • Requiere el modelo gpt-5.1-codex-max con un gran esfuerzo de razonamiento
  • Uso obligatorio de un modelo específico y esfuerzo de razonamiento
  • Compatibilidad con el servidor proxy CLI de Claude Code necesaria

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is codex?

Perfecto para agentes de codificación que necesitan automatización avanzada y optimización del flujo de trabajo con Claude Code y el modelo gpt-5.1-codex-max Un servidor proxy multi-tenant para Claude Code que permite la conmutación automática y la administración web

How do I install codex?

Run the command: npx killer-skills add yxhpy/qcc_plus/codex. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for codex?

Key use cases include: Automatizar tareas de codificación con el modelo gpt-5.1-codex-max, Optimizar la automatización del flujo de trabajo para los desarrolladores, Habilitar el soporte multi-tenant y el failover automático para tareas de codificación.

Which IDEs are compatible with codex?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for codex?

Requiere el modelo gpt-5.1-codex-max con un gran esfuerzo de razonamiento. Uso obligatorio de un modelo específico y esfuerzo de razonamiento. Compatibilidad con el servidor proxy CLI de Claude Code necesaria.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add yxhpy/qcc_plus/codex. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use codex immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Imported Repository Instructions

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Supporting Evidence

codex

Descubre cómo utilizar la herramienta Codex con Claude Code para crear un servidor proxy multi-tenant con capacidad de conmutación automática y...

SKILL.md
Readonly
Imported Repository Instructions
The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.
Supporting Evidence

Codex Skill Guide

Running a Task

  1. Always use model gpt-5.1-codex-max with reasoning effort high for all Codex runs:
    • Model: gpt-5.1-codex-max (mandatory, do not change)
    • Reasoning effort: high (mandatory, do not change)
    • If the user mentions other model names (gpt-5, gpt-5-codex-max, gpt-5-codex), always use gpt-5.1-codex-max instead.
    • Clearly state in your summary that model gpt-5.1-codex-max with high reasoning effort was used.
  2. Select the sandbox mode required for the task; default to --sandbox read-only for analysis-only tasks, and use --sandbox workspace-write when edits are needed. Only consider --sandbox danger-full-access when the user’s request clearly requires network or broad system access.
  3. Assemble the command with the appropriate options:
    • -m, --model <MODEL>
    • --config model_reasoning_effort="<high|medium|low>"
    • --sandbox <read-only|workspace-write|danger-full-access>
    • --full-auto
    • -C, --cd <DIR>
    • --skip-git-repo-check
  4. Always use --skip-git-repo-check.
  5. When continuing a previous session, use codex exec --skip-git-repo-check resume --last via stdin. When resuming don't use any configuration flags unless explicitly requested by the user e.g. if he species the model or the reasoning effort when requesting to resume a session. Resume syntax: echo "your prompt here" | codex exec --skip-git-repo-check resume --last 2>/dev/null. All flags have to be inserted between exec and resume.
  6. IMPORTANT: By default, append 2>/dev/null to all codex exec commands to suppress thinking tokens (stderr). Only show stderr if the user explicitly requests to see thinking tokens or if debugging is needed.
  7. Run the command, capture stdout/stderr (filtered as appropriate), and summarize the outcome for the user.
  8. After Codex completes, inform the user: "You can resume this Codex session at any time by saying 'codex resume' or asking me to continue with additional analysis or changes."

Quick Reference

Use caseSandbox modeKey flags
Read-only review or analysisread-only--sandbox read-only 2>/dev/null
Apply local editsworkspace-write--sandbox workspace-write --full-auto 2>/dev/null
Permit network or broad accessdanger-full-access--sandbox danger-full-access --full-auto 2>/dev/null
Resume recent sessionInherited from originalecho "prompt" | codex exec --skip-git-repo-check resume --last 2>/dev/null (no flags allowed)
Run from another directoryMatch task needs-C <DIR> plus other flags 2>/dev/null

Following Up

  • After every codex command, summarize what was done, propose concrete next steps, and, if needed, ask focused follow-up questions only about the task itself (not about model or reasoning-effort choices).
  • When resuming, pipe the new prompt via stdin: echo "new prompt" | codex exec resume --last 2>/dev/null. The resumed session automatically uses the same model, reasoning effort, and sandbox mode from the original session.
  • Restate that gpt-5.1-codex-max with high reasoning effort was used, along with the sandbox mode, when proposing follow-up actions.

Error Handling

  • Stop and report failures whenever codex --version or a codex exec command exits non-zero; request direction before retrying.
  • Before you use high-impact flags like --full-auto or --sandbox danger-full-access, make sure the user’s request clearly implies this level of automation or access; you do not need to ask them to choose model or reasoning-effort.
  • When output includes warnings or partial results, summarize them and ask how to adjust using AskUserQuestion.

Habilidades relacionadas

Looking for an alternative to codex or another community skill for your workflow? Explore these related open-source skills.

Ver todo

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
Inteligencia Artificial

widget-generator

Logo of f
f

Generar complementos de widgets personalizables para el sistema de feeds de prompts.chat

149.6k
0
Inteligencia Artificial

flags

Logo of vercel
vercel

El Marco de React

138.4k
0
Navegador

pr-review

Logo of pytorch
pytorch

Tensores y redes neuronales dinámicas en Python con fuerte aceleración de GPU

98.6k
0
Desarrollador