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.
git clone --depth 1 https://github.com/kpkhxlgy0/claude-openai-gpt-imageWrote 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/commands/kpkhxlgy0/claude-openai-gpt-image/setup)<a href="https://agentmods.dev/commands/kpkhxlgy0/claude-openai-gpt-image/setup"><img src="https://agentmods.dev/badge/commands/kpkhxlgy0/claude-openai-gpt-image/setup/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/commands/kpkhxlgy0/claude-openai-gpt-image/setup"><img src="https://agentmods.dev/badge/commands/kpkhxlgy0/claude-openai-gpt-image/setup.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.00013 | $0.00398 |
| Opus 5 | $0.00006 | $0.00199 |
| Sonnet 5 | $0.00003 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
setup 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 10d 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.
What it actually says
Invoke only get_status, exactly once. Do not invoke any image-generation or image-editing tool as part of setup or diagnosis.
If get_status is unavailable, cannot be invoked, or does not return a real current-session MCP tool result, stop. Report that setup could not inspect the plugin; do not infer status from files, prior messages, or other tools.
If the result reports an error or omits any required field, stop. Require the returned fields below to have their documented types before reporting status or giving configuration advice.
Do not use Bash, Write, Agent, local scripts, direct SDK or HTTP calls, or handwritten JSON-RPC as a fallback.
Report these returned fields without guessing or revealing configuration values:
api_key_configuredbase_url_configuredandbase_url_valid- approved
workspace_roots default_relative_output_dir- model and server version
If the API key is missing, direct the user to the interactive Claude Code TUI: run /plugin, open Installed, select gpt-image-2, and choose Configure options. The key belongs only in the sensitive OpenAI API key field. Never ask the user to paste or reveal it.
If the Base URL is invalid, or the user expected a custom URL but base_url_configured is false, direct them to the same Configure options screen. Explain that the default is the official OpenAI Base URL and that a custom endpoint should usually include /v1 because the plugin does not append it automatically.
Claude Desktop itself does not provide this configuration screen. After a setting change is saved, tell the user to restart Claude Desktop or start a new Desktop Local session so the MCP process loads the new configuration.
Conclude explicitly: No paid API request was made, and no image API request was made.
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.
- 10d ago First seen · 28 lines · 13 tokens per session scan A 0bf555e380d0
setup is a command published in the GitHub repository kpkhxlgy0/claude-openai-gpt-image (0 stars, last pushed 21d ago), licensed MIT. It adds 13 tokens to every session and 398 once invoked, about $0.0001 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.