OpenAI Developers for Claude Code is a Claude Code plugin bundle that connects OpenAI developer documentation and workflow guidance to Claude Code. It helps users build AI applications, agents, and ChatGPT Apps from Claude Code, including setup, troubleshooting, Agents SDK development, and app submission. The catalogue entries are the plugin's skills, plugin metadata, and documentation MCP integration.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add openai/openai-developers-for-claude --skill chatgpt-app-submissiongit clone --depth 1 https://github.com/openai/openai-developers-for-claudeWrote 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/openai/openai-developers-for-claude/chatgpt-app-submission)<a href="https://agentmods.dev/skills/openai/openai-developers-for-claude/chatgpt-app-submission"><img src="https://agentmods.dev/badge/skills/openai/openai-developers-for-claude/chatgpt-app-submission/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/openai/openai-developers-for-claude/chatgpt-app-submission"><img src="https://agentmods.dev/badge/skills/openai/openai-developers-for-claude/chatgpt-app-submission.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.00054 | $0.02146 |
| Opus 5 | $0.00027 | $0.01073 |
| Sonnet 5 | $0.00011 | $0.00429 |
| Haiku 4.5 | $0.00005 | $0.00215 |
Grade A, and why
chatgpt-app-submission 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 11d 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.
This is a copy
88% identical to chatgpt-app-submission — 30 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ChatGPT App Submission
Use this skill when a developer needs a chatgpt-app-submission.json file for a ChatGPT Apps submission. The file is uploaded in the Apps submission form to fill out parts of App Info, MCP Server, and Testing.
Workflow
- Inspect the MCP server codebase from the current working directory.
- Read repo metadata, package metadata, README files, app manifests, tool descriptors, resource templates, and widget metadata needed to understand the app.
- Find every exposed MCP tool, its declared
readOnlyHint,openWorldHint, anddestructiveHintannotations, and whether it declaresoutputSchema. - Read each tool implementation and any called helper functions needed to understand side effects.
- Compare tool annotations, tool names, tool descriptions, and CSP values against actual behavior. If any value is missing, stale, misleading, or inconsistent, ask the developer for approval before updating source.
- Generate concise review-facing app info suggestions, tool hint justifications, positive test cases, and negative test cases.
- Write
chatgpt-app-submission.jsonin the current working directory. - Print review-check findings and any missing
outputSchemawarnings in the final response, and explain what the developer should do with each finding before submission.
Do not infer behavior from the tool name alone. Use the real tool implementation and declared annotations. If a tool calls into another module or API client, inspect enough of that path to know whether it reads, writes, deletes, sends, publishes, or changes external state.
App Info Rules
Suggest app info from source-of-truth project metadata and the tool behavior you inspected. Keep it plain-language and submission-review-facing.
display_name: use the product or app name from repo metadata, package metadata, README, manifest, or existing configuration. Keep it short enough for the submission form.subtitle: summarize what the app does in one short functional phrase, not marketing copy. It must be 30 characters or less.description: describe concrete user value and the main workflows the tools support.category: choose one ofBUSINESS,COLLABORATION,DESIGN,DEVELOPER_TOOLS,EDUCATION,ENTERTAINMENT,FINANCE,FOOD,LIFESTYLE,NEWS,PRODUCTIVITY,SHOPPING, orTRAVEL.
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.
- 11d ago First seen · 143 lines · 54 tokens per session scan A fbb2a7c8aeec
chatgpt-app-submission is a skill published in the GitHub repository openai/openai-developers-for-claude (23 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 2,146 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to chatgpt-app-submission, differing in 30 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…