chatgpt-pro-consult

chatgpt-pro-consult is a skill for Claude Code, Codex from adamallcock/codex-chatgpt-control. It costs 35 tokens per session (2,938 once invoked), scanned A, original, MIT.

A workflow for asking the visible ChatGPT app for a focused second opinion using its Pro intelligence setting. It is an older alias for the newer ChatGPT delegation workflow.

In plain words
What is it for?
Requesting critical reviews, planning feedback, synthesis, or long-form opinions through the visible ChatGPT website.
Why use it?
It helps obtain another review or synthesis when the task benefits from a separate ChatGPT consultation, while keeping use visible and requiring approval for sensitive material.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is ../../runtime/import-chatgpt-control.mjs.

Good fit Requesting critical reviews, planning feedback, synthesis, or long-form opinions through the visible ChatGPT website.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/adamallcock/codex-chatgpt-control
agentmods
npx agentmods add skills/adamallcock/codex-chatgpt-control/chatgpt-pro-consult

Made for: Claude Code, Codex.

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 chatgpt-pro-consult

README.md
[![agentmods](https://agentmods.dev/badge/skills/adamallcock/codex-chatgpt-control/chatgpt-pro-consult/github.svg)](https://agentmods.dev/skills/adamallcock/codex-chatgpt-control/chatgpt-pro-consult)
Your own site
<a href="https://agentmods.dev/skills/adamallcock/codex-chatgpt-control/chatgpt-pro-consult"><img src="https://agentmods.dev/badge/skills/adamallcock/codex-chatgpt-control/chatgpt-pro-consult/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 chatgpt-pro-consult

Your own site · 80×15
<a href="https://agentmods.dev/skills/adamallcock/codex-chatgpt-control/chatgpt-pro-consult"><img src="https://agentmods.dev/badge/skills/adamallcock/codex-chatgpt-control/chatgpt-pro-consult.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,938 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Agent Snooping · line 51
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
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.00035 $0.02938
Opus 5 $0.00017 $0.01469
Sonnet 5 $0.00007 $0.00588
Haiku 4.5 $0.00003 $0.00294

Measured 12d ago against content hash 5e90b80f0a79, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

chatgpt-pro-consult 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 12d 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/codex-chatgpt-control/skills/chatgpt-pro-consult/SKILL.md · 290 lines

How it starts

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

ChatGPT Pro Consult

This is a backward-compatible skill alias. Prefer chatgpt-delegate for new work because it chooses between Chat, Work, and official Codex based on the job and uses the strict experience/configuration APIs.

Use this alias when an existing workflow or user explicitly requests the visible Chat Pro intelligence setting for a focused consultation. Typical uses are critical review, synthesis, planning review, and a long-form second opinion through the user's ChatGPT subscription.

This skill is a thin workflow over the codex-chatgpt-control plugin. Use the snippets below for ordinary consults, but switch to the full codex-chatgpt-control skill as soon as bridge bootstrap, tab reuse, file attach, send, wait, read, or selector diagnosis becomes the main issue.

Guardrails

  • This sends prompt and attachment content to ChatGPT web. Do not send secrets, credentials, private source material, financial details, legal evidence, medical details, or sensitive personal data unless the user clearly approved that disclosure.
  • Use only visible ChatGPT web through the Codex/browser bridge. Do not replicate private ChatGPT network calls, read cookies, inspect localStorage/sessionStorage, or extract hidden auth headers.
  • Make Pro selection explicit with experience: "chat" and configuration: { intelligence: "Pro" }. The strict configuration API handles older and newer visible pickers and verifies the postcondition. If the SDK cannot verify Pro, stop and report the blocker and visible candidate labels.
  • Call experience.open({ experience: "chat" }) through the workflow even when Work is currently visible; do not assume the current ChatGPT pane is Chat.
  • Prefer a fresh thread unless the user asked to continue a specific ChatGPT thread.
  • Return Markdown by default. Use redacted reports by default; raw prompt/response content is opt-in only.
  • Treat ChatGPT Pro output as another model's judgment, not verified truth. Verify current, legal, medical, financial, or high-stakes claims with primary sources.
  • Keep each Codex tool call below the host call ceiling. Do not ask one JS call to wait for a long Pro response. Submit the prompt under Pro first, then poll/read in bounded chunks.

Read the full file on GitHub · 290 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 12d ago First seen · 290 lines · 35 tokens per session scan A 5e90b80f0a79

Subscribe to this mod's changes

chatgpt-pro-consult is a skill published in the GitHub repository adamallcock/codex-chatgpt-control (400 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 2,938 once invoked, about $0.0002 per session on Opus 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-08-30.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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

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