Credentials. Setup asks you to complete Sign in with ChatGPT device authorization, so only approve it on a machine and account you control.
Who it is forA solo creator or developer with a ChatGPT subscription who needs a quick illustration for a blog post, slide, or project page and works inside Codex or Claude Code.
The problemImage generation usually means a separate tool, a separate bill, or an API key. The user wants images without leaving the coding agent.
The outcomeA PNG saved in /generated-images inside the active project, returned as a PATH and an inline Markdown link.
What you need first
- A ChatGPT or Codex plan that permits image generation (the README says Codex image generation is not available on the Free plan)
- Node.js 22 or newer
- Git, for installing from GitHub
- Codex CLI signed in with ChatGPT, or a host that provides subscription-native image_gen
Steps
- Paste the install prompt from the README into Codex, Claude Code, or Google Antigravity, and follow the Sign in with ChatGPT device authorization when asked.
- Wait for the setup to report readiness. The README states that no image is generated during setup.
- In Codex, type
$gpt-image Create a cozy reading room at sunset, 16:9, high quality.In Claude Code, use/gpt-imagewith the same request. - Open the returned PATH in /generated-images and check the image against your request.
Prompt for your agent
Install GPT Image Skill from https://github.com/GENEXIS-AI/gpt-image-skill using the AGENT_INSTALL.md contract, then generate one image of <subject> at <aspect ratio> with high quality. Expect a PNG under /generated-images and a PATH=... line in the output. Verify the file exists and that the output did not use OPENAI_API_KEY or the Images API.
Caveat. Generation draws on included ChatGPT or Codex usage, so a Free plan account cannot complete these steps.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page