by GENEXIS-AI
Generate GPT images from Codex or Claude Code using a ChatGPT subscription, without the Images API.
Unlocks once the catalog security scan passes (runs nightly).
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
# Add to your Claude Code skills
git clone https://github.com/GENEXIS-AI/gpt-image-skillGuides for using ai agents skills like gpt-image-skill.
Generate and edit GPT images from Codex, Claude Code, or another compatible local agent through the user's ChatGPT subscription. Direct prompts stay unchanged; when the user delegates several different designs, the agent develops a distinct image-ready prompt for each concept. Real reference files pass into generation, results stay in the active project, and ready outputs run with bounded parallelism.
install skill → Sign in with ChatGPT → direct prompt or delegated concept prompts + local image inputs
→ single generate or bounded parallel batch
→ built-in $imagegen → <project>/generated-images/*.png
This repository does not call the OpenAI Images API and does not create a separately billed Images API request. Built-in image generation still consumes included ChatGPT/Codex usage and remains subject to plan and workspace limits. OpenAI notes that image generations use included limits 3–5× faster on average than similar non-image turns, depending on quality and size, so parallel batches should stay intentional and small.


Paste this into Codex, Claude Code, or another local coding agent:
Install and verify GPT Image Skill for the current user from:
https://github.com/GENEXIS-AI/gpt-image-skill
For this task, I authorize read-only environment checks; a persistent clone or safe fast-forward update;
user-level installation of missing Git, a supported Node.js 22+ LTS, and Codex CLI;
creation of the gpt-image links for Codex and Claude Code; and starting Sign in with ChatGPT device authorization.
Read AGENT_INSTALL.md at the repository root and follow it as the one-time installation contract.
Do not use the Images API, OPENAI_API_KEY, or API-key login. Do not generate a live image yet.
Pause only if administrator privileges are required, an unrelated existing path would be changed,
local changes would be discarded, or existing Codex authentication would need to be replaced.
Otherwise, install the required components, run bootstrap --target all --yes --json,
and continue until bootstrap's consolidated readiness report shows best_practice_pass=true.
Do not add a separate doctor, plan, inspect, or no-image generation check when bootstrap passes.
Finally, report the persistent clone path, both installed skill paths, and ChatGPT-auth evidence.
Then give me the brief getting_started guide in my language: common aspect ratios,
quality phrases, one creation example, and one reference or revision example.
Do not use unexplained jargon such as "dry-run"; call it a setup check that does not create an image.
This prompt authorizes ordinary user-level setup without authorizing administrator elevation, destructive changes, replacement of existing authentication, a live generation, or a GitHub Star. The full boundary is in AGENT_INSTALL.md.
After setup, invoke $gpt-image in Codex or /gpt-image in Claude Code. The host loads the concise skill only for image tasks; it does not need to reread this README on every request.
The installing agent should end with a small guide like this, translated into the user's language:
GPT Image Skill is ready. No image was generated during setup.
Common aspect-ratio requests: 1:1, 16:9, 9:16, 4:3, 3:4
Quality phrases: draft, high quality, high detail / final quality
Try:
$gpt-image Create a cozy reading room at sunset, 16:9, high quality.
/gpt-image Use @references/character.png as the character reference and place it in a rainy city, 9:16, high quality.
These are common natural-language requests, not a fixed API size list. Other framing or dimension requests can be written normally, and exact pixel dimensions may vary with built-in image generation. The guide appears once after installation rather than after every image.
For one direct image or edit, the skill forwards the user's image request unchanged. It does not “improve” a short prompt with unsolicited details. A request such as “make five different poster designs” is different: it explicitly asks the agent to develop five creative concepts. The agent preserves the shared subject, references, brand, text, ratio, and other constraints, then sends one complete, meaningfully different image prompt per output. Job numbers remain in IDs and filenames, never in image prompts.
The bridge requires a readable local PNG, JPEG, or WebP path for each reference. It passes those files into the actual $imagegen call. It never replaces an unresolved reference with a text description and continues anyway.
In Claude Code:
@path/to/image.png or an explicit filesystem path.codex exec process.<project>/generated-images/inputs/ and uses the copy.~/.claude/image-cache; choosing “the newest image” could select the wrong or private file.Each bridge invocation is ephemeral. For “change the result you just made,” the agent must use the previous generated output as the next --edit-target and reattach every still-needed reference. Reusing the original source is a different operation and loses the prior edit.
The default path is:
quick ChatGPT-auth check → one generation → minimal PNG sanity check → PATH + inline Markdown
Planning, the setup check that does not create an image (--dry-run), capabilities --json, inspect --input, and detailed JSON remain available for troubleshooting. They are not required before a normal image request.
generate remains the one-image happy path. For two or more outputs, the skill automatically batches every job whose inputs already exist. Different design concepts run independently; same-design variants may run together while reading one shared edit target or design reference. Only an output-to-input dependency creates another stage. The batch checks ChatGPT auth once and uses default concurrency 2, maximum 4, with no Doctor, planning, inspection, or automatic retries per job.
$imagegen under Sign in with ChatGPTimage_gen tool directly when the calling host already exposes oneOPENAI_API_KEY, API-key Codex login, and Images API fallbackgpt-image skill for Codex and Claude CodePATH=... and absolute MARKDOWN=... after normal generation| Intent | Bridge arguments |
|---|---|
| Text-to-image | --mode generate |
| New image guided by a reference | --mode generate --reference PATH |
| Multiple references | Repeat --reference; add matching --reference-role only for explicit roles |
| Change an existing image | --mode edit --edit-target PATH |
| Change the last generated image | Use the last returned path as the new --edit-target |
| Variation | --mode variation --edit-target PATH |
| Transparent output | Use --background transparent only when requested |
| Same design, different styles | Repeat --mode variation --edit-target SAME_PATH in a batch |
| Same identity, different scenes | Repeat --mode generate --reference SAME_PATH in a batch |
| Different designs in parallel | Give each batch job its own prompt and references |
The edit target is Image 1. Supporting references follow in command-line order.
image_gen.| Environment | Status | Keep together |
|---|---|---|
| macOS | Supported | macOS Node.js, Codex, clone, and workspace |
| Linux | Supported | Linux Node.js, Codex, clone, and workspace |
| Native Windows | Supported | Windows Node.js, Codex, junctions, and workspace |
| WSL2 | Supported | Keep the complete toolchain on the Linux side |
| WSL1 | Unsupported | Move to WSL2 or native Windows |
Use a persistent clone because the installed skill links point to it.
REPOSITORY_URL="https://github.com/GENEXIS-AI/gpt-image-skill"
INSTALL_DIR="${XDG_DATA_HOME:-$HOME/.local/share}/gpt-image-skill"
git clone "$REPOSITORY_URL" "$INSTALL_DIR"
cd "$INSTALL_DIR"
node ./gpt-image/scripts/validate_skill.mjs
node ./gpt-image/scripts/gpt_image.mjs bootstrap --target all --yes --json
Keep WSL2 clones under the Linux h
gpt-image-skill is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by GENEXIS-AI. Generate GPT images from Codex or Claude Code using a ChatGPT subscription, without the Images API. It has 52 GitHub stars.
gpt-image-skill's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/GENEXIS-AI/gpt-image-skill" and add it to your Claude Code skills directory (see the Installation section above).
gpt-image-skill is primarily written in JavaScript. It is open-source under GENEXIS-AI on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh gpt-image-skill against similar tools.
No comments yet. Be the first to share your thoughts!