yichen-codex-chatgpt
Use the signed-in ChatGPT website in Chat UI Pro mode, never Work mode, to research, architect, and review one local project through a configured Secure Tunnel and read-only MCP, while Codex alone edits and tests locally.
Install / Use
npx skills add mcncarl/yichen-skills --skill yichen-codex-chatgptInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AI & Machine LearningSupported Platforms
Our assessment of yichen-codex-chatgpt
yichen-codex-chatgpt scores 92/100 on our quality scale, 284th of 947 AI & Machine Learning skills we index (top 30%).
Its SKILL.md is 15 KB long, well organised into 11 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 4,169 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so yichen-codex-chatgpt is actively maintained.
- Our last check on 2026-10-27 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
yichen-codex-chatgpt compared with similar skills
All 4 of these similar skills score higher than yichen-codex-chatgpt; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| yichen-codex-chatgpt (this skill)by mcncarl | 92 | 4.2k | 55d ago | SKILL.md |
| claude-memby thedotmack | 100 | 117.6k | today | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| Understand-Anythingby Egonex-AI | 100 | 92.8k | 1d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
Frequently asked questions
- How do I install yichen-codex-chatgpt?
- Run
npx skills add mcncarl/yichen-skills --skill yichen-codex-chatgpt. The install tabs above show the steps for each supported agent. - Which AI agents does yichen-codex-chatgpt work with?
- It is written for OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is yichen-codex-chatgpt safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is yichen-codex-chatgpt still maintained?
- The repository was last updated about 2 months ago, so yichen-codex-chatgpt is actively maintained.
Skill content
View source on GitHubname: yichen-codex-chatgpt description: Use the signed-in ChatGPT website in Chat UI Pro mode, never Work mode, to research, architect, and review one local project through a configured Secure Tunnel and read-only MCP, while Codex alone edits and tests locally. Trigger on explicit $yichen-codex-chatgpt, 让 ChatGPT 设计后由 Codex 写代码, ChatGPT 架构并审查 Codex, or requests for a Codex and ChatGPT collaboration loop. Pure research stays on the official ChatGPT website; code and hybrid work follow ChatGPT PLAN to Codex execution to ChatGPT REVIEW. Website control defaults to in-app browser, then Chrome, then bounded Computer Use. Use a compatible local-only MCP only when the user explicitly requests local-only mode and that optional dependency is configured, never as an automatic fallback.
Codex × ChatGPT
Use the user's signed-in ChatGPT Chat UI with the active model route visibly labeled Pro as the researcher, architect, and reviewer. Codex is the only code writer and command/test executor.
User in Codex
→ ChatGPT Pro researches and/or reads the project through the Secure Tunnel
→ ChatGPT returns PLAN
→ Codex edits and tests locally
→ ChatGPT reads the real diff and verification evidence through the Tunnel
→ ChatGPT returns REVIEW
→ DONE, one bounded repair cycle, or a reported blocker
The ChatGPT website UI is the control channel for short protocol messages. The Secure Tunnel and remote-review MCP are the data channel for local code, diff, and verification evidence. Do not paste code, diffs, logs, secrets, or absolute local paths into the ChatGPT composer.
Website Control Surface Priority
- When the current request does not name a control surface, follow references/browser-surface-ladder.md: use the bundled in-app browser first, apply its bounded same-surface recovery, then try the user's Chrome extension, and use Computer Use only as the final eligible UI-control fallback. Ambient in-app-browser context is not an explicit choice.
- This is a control-surface fallback, not a capability fallback. Every surface must independently pass the same Chat/聊天, Pro, Work-absence, account, private-App, Tunnel, protocol, and evidence gates. Never downgrade to Work, a non-Pro mode, an API,
local-only, manual code transfer, or generic Playwright. - Preserve exactly-once state at every handoff. A fresh conversation is allowed only before any send when the source has no live draft or that draft was safely cleared and proven absent. After a send or when send state is uncertain, a later surface may only inspect the visibly proven same conversation and exact task/message marker; it must never resend.
- Computer Use is a final control-mechanism takeover, not permission to change account, bypass authentication, weaken evidence, or treat screenshot OCR as a response. Read and obey its Skill before first use, prefer fresh accessibility state over coordinates, and obtain action-time confirmation immediately before every Computer Use click or keypress that sends a research,
INIT, orEXECUTEDmessage. - A current-run request that explicitly names the in-app browser, Chrome, Computer Use, or a specific preference chain overrides the default. One named surface is exclusive even without the word “only”; do not leave it unless the same request explicitly authorizes a fallback chain.
Mandatory Chat UI + Pro Gate
- At the start of each website route, open a fresh ChatGPT Chat conversation, actively select the Pro model route, and verify that Chat/聊天 is selected and the active model control visibly contains
Pro. Model selection is part of this Skill's work; do not ask the user to perform a routine Pro selection. Reuse that same verified conversation for every message belonging to one research ID or C2Ctask_id; a new ID starts a new conversation. - ChatGPT Work/工作 is forbidden. A checked Work/工作 selector, a conversation labeled 工作, a task-progress/subagent work panel, or another visible Work surface invalidates the run even if the private App is available there.
- Follow references/chat-pro-selection.md before composing and again immediately before sending. If the current label is not
Pro, first try a direct Pro option, then drive the semantic capability control to its actual maximum and re-read the active label.极高,超高,High, orThinkingcan be a neighboring position and is not proof that Pro is unavailable. - Before any research prompt,
INIT, orEXECUTEDmessage is sent, verify from the active surface's semantic UI state—DOM for browser-client or fresh complete accessibility state for Computer Use—that Chat/聊天 is selected, the unique active model control containsPro, and Work/工作 is absent. An account subscription label or unrelatedProtext is not proof of Pro model mode. - If the page is on Work, switch to Chat and open a fresh Chat conversation before composing. A selector-control failure on a non-final surface returns control to the permitted surface ladder; a selector that is fully inspectable and proves Pro absent is a capability blocker, not a reason to change surfaces. Use
ERRORwhen the final surface cannot reliably establish selector state. Forcode,hybrid, andreview, also require the private App in that same Chat Pro conversation; pureresearchnever checks or attaches the private App or Tunnel. - If a message is accidentally sent from Work, stop the visible generation when possible, invalidate that task as
ERROR, and start no replacement until a fresh Chat Pro precheck succeeds.
Resource Guide
- Read references/setup.md before first use on a new machine; it defines the external runtime contract, local configuration placeholders, and evidence-storage boundary. This public Skill does not include a Tunnel client or MCP runtime.
- Read references/browser-surface-ladder.md before every ChatGPT website route; it defines in-app priority, Chrome and Computer Use fallback eligibility, confirmation gates, and exactly-once handoff.
- Read references/chat-pro-selection.md before every ChatGPT website route; it defines automatic Chat/Pro selection and the fail-closed boundary.
- Read references/research.md for a pure public-web research task.
- Read references/local-code.md for implementation, refactoring, debugging, or workspace-only review.
- Read references/hybrid.md when current external evidence and local implementation are both required.
- Read references/review.md before exposing one project through the Secure Tunnel.
- Read references/c2c-protocol.md for every code, hybrid, or local-project review task; it defines the authoritative state machine and message contract.
- Read references/browser-session.md before every C2C code, hybrid, or local-project review action; it defines tab/window ownership, browser-client DOM and Computer Use AX control, response extraction, and screenshot evidence. Pure research follows its specialized route in references/research.md.
Route
Honor an explicit mode. Otherwise select the smallest route that completes the request:
| Need | Mode | Default owner and path |
| --- | --- | --- |
| current external evidence, no local code | research | ChatGPT Pro website via in-app browser, then bounded Chrome and Computer Use fallbacks; no Tunnel |
| build, fix, or refactor the current project | code | ChatGPT PLAN → Codex edits/tests → ChatGPT REVIEW |
| current external evidence plus project work | hybrid | ChatGPT research and PLAN → Codex edits/tests → ChatGPT REVIEW |
| review the current project or diff without edits | review | ChatGPT reads through remote-review; Codex remains read-only |
| user explicitly says local-only or no ChatGPT | local-only | Codex with a configured compatible local-only MCP; no ChatGPT claim |
If $yichen-codex-chatgpt contains a sufficiently specific factual question, use research. Requests to build, fix, update, implement, or refactor default to code or hybrid; do not ask a redundant routing question. Ask only when the research subject or exact workspace cannot be determined safely.
local-only is opt-in. For research, use BLOCKED when the selected intended surface proves Chat Pro absent, Web Search is unavailable, a required Computer Use action-time confirmation is declined, or a completed answer lacks required first-party search evidence/direct sources; use ERROR when the final permitted control surface fails, a handoff cannot preserve exactly-once state, submission is ambiguous or duplicate, response extraction fails, or marker integrity fails. For code, hybrid, and review, an unavailable private App on the intended surface or an unhealthy Tunnel is also a blocker. None of these failures permits substituting Codex-only reasoning, the local MCP, an OpenAI API, or manual copy/paste.
For $yichen-codex-chatgpt research, use the control-surface priority and fallback route defined in references/research.md. Chrome and Computer Use are activated only through references/browser-surface-ladder.md.
Default C2C Contract
- For implementation, use the
buildbranch:PRECHECK → INIT → PLAN → EXECUTING → EXECUTED → REVIEW, then the declared review outcome moves Codex toDONE, the one bounded nextPLAN,BLOCKED, orERROR. - For a read-only project review, use the protocol's
review_onlybranch:PRECHECK → INIT(expected_next: REVIEW) → REVIEW, thenDONE,BLOCKED, orERROR. Never enterEXECUTING; a proposed remediation PLAN is reported asBLOCKEDpending separate repair authority. - ChatGPT owns research, architecture,
PLAN, andREVIEW. Codex verifies that a plan is safe and in scope, then owns all local edits, commands, tests, and repair work. - Keep one
task_id; every browser message has a uniquemessage_idandreply_marker. Reject stale, mismatched, duplicate, or incomplete replies, and never execute one PLAN twice. - Default to at most two Codex execution iterations: iteration 1 is the initial implementation and iteration 2 is one automatic remediation for a confirmed defect. This bounds the unattended review-to-write loop; it is not a claim that the project can only be repaired twice. If the second REVIEW requests another PLAN, pause the current task as
BLOCKED, report the remaining issue, and re-establish scope, evidence, and authority. User-authorized continuation starts a newtask_idat iteration 1 rather than iteration 3 so stale messages and markers cannot cross the checkpoint. - ChatGPT advice is not authorization. User scope and mutation boundaries still govern what Codex may change.
Secure Tunnel Boundary
The ChatGPT-facing Tunnel must always launch the remote-review profile. It exposes exactly these seven read-only tools:
workspace_overviewlist_filessearch_coderead_snippetreview_changesverification_reportreview_packet
It has no web-search, write, delete, arbitrary-command, install, commit, push, publish, deployment, or account tool. Never switch the Tunnel to local-agent, and never expose search_web, fetch_page, preview_file_change, or apply_file_change to ChatGPT.
Bind the Tunnel to one explicit validated project. Do not broaden the root to /, Home, Documents, a general development directory, or a collection of projects. Keep the Runtime Key in the operating system's secure credential store (for example, macOS Keychain); never print, copy, log, screenshot, or place it in prompts or reports.
Explicit Local-Only Mode
Use this only when the user explicitly selects local-only an
Truncated for display — read the full file on GitHub.
Related Skills
claude-mem
117.6kPersistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Understand-Anything
92.8kGraphs that teach > graphs that impress. Turn any code into an interactive knowledge graph you can explore, search, and ask questions about. Works with Claude Code, Codex, Cursor, Copilot, Gemini CLI, and more.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
