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 tallesborges/zdx --skill imaginegit clone --depth 1 https://github.com/tallesborges/zdxWrote 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/tallesborges/zdx/imagine)<a href="https://agentmods.dev/skills/tallesborges/zdx/imagine"><img src="https://agentmods.dev/badge/skills/tallesborges/zdx/imagine/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/tallesborges/zdx/imagine"><img src="https://agentmods.dev/badge/skills/tallesborges/zdx/imagine.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.03934 |
| Opus 5.5 | $0.00022 | $0.01574 |
| Sonnet 5.5 | $0.00011 | $0.00787 |
| Haiku 4.5 | $0.00006 | $0.00393 |
Grade A, and why
imagine 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 28d 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.
How it starts
The opening of the file, as written. The whole thing — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Imagine – Image Generation & Editing via zdx imagine
Generate images from text prompts or edit existing images using Gemini, OpenAI, or Alibaba (Qwen-Image) image models. Supports text-to-image generation, image editing (inpainting, outpainting, style transfer), and multi-image composition.
CLI reference
zdx imagine --prompt <PROMPT> [OPTIONS]
Options:
-p, --prompt <PROMPT> Text prompt (required)
-s, --source <IMAGE> Source image for editing (repeatable for multi-image)
-o, --out <PATH> Output path — written exactly as given (default: $ZDX_HOME/artifacts/image-<timestamp>.<ext>)
--model <MODEL> Model override (default: gemini:gemini-3.1-flash-image-preview)
--aspect <RATIO> Aspect ratio (Gemini only; see table below)
--size <SIZE> 512px | 1K (default) | 2K | 4K
Output: prints the exact saved file path(s) to stdout. --out is honored literally; the model picks the image format (often JPEG for Gemini), so a file named .png may actually hold JPEG bytes. That is fine — zdx reads images by content, not extension. Use --out to control the path and always view/attach the printed path.
When running inside zdx (TUI, bot, or CLI), $ZDX_ARTIFACT_DIR is the preferred output location. Pass it via --out:
zdx imagine -p "..." --out "$ZDX_ARTIFACT_DIR/descriptive-name.png"
If no --out is given, images default to $ZDX_HOME/artifacts/.
Provider guidance
- Default: If you do not pass
--model,zdx imagineusesgemini:gemini-3.1-flash-image-preview. - OpenAI support:
zdx imaginealso supports bothopenai:gpt-image-2andopenai-codex:gpt-image-2. - Preferred OpenAI path: When using OpenAI, prefer
openai-codex:gpt-image-2unless the user explicitly asks for plainopenai:gpt-image-2or for GPT Image 2.5. - GPT Image 2.5 (explicit selection, API key):
openai:gpt-image-2.5-flare(fast, the default choice for most work) andopenai:gpt-image-2.5-sunburst(higher precision for detailed edits, slower). Dated snapshots such asopenai:gpt-image-2.5-flare-2026-09-08also work. Use them only when the user asks for GPT Image 2.5 or the newest OpenAI image model. RequiresOPENAI_API_KEY. - Codex is server-managed:
openai-codex:*image requests run on the ChatGPT subscription, and the backend picks the image engine, size, and quality itself. Probes showed it ignores the requested image model,--size, and quality, and it never reports which model ran.openai-codex:gpt-image-2.5-*is accepted but not honored as a selection;zdx imagineprints a warning on stderr. Do not tell the user Codex gave them Image 2 or Image 2.5 specifically. For an explicit variant, useopenai:gpt-image-2.5-flareor-sunburst. - Alibaba (Qwen-Image) support:
zdx imaginesupportsalibaba:qwen-image-3.0-pro,alibaba:qwen-image-3.0, andalibaba:qwen-image-2.0-pro— combined text-to-image + editing models on Alibaba DashScope. RequiresALIBABA_API_KEY. Use them when the user asks for Qwen/Alibaba image generation. - Preferred Alibaba path: Use
alibaba:qwen-image-3.0-pro. It is the strongest of the three at dense layouts, small text (~10px), and multilingual typography. Fall back toalibaba:qwen-image-3.0for cheaper/faster runs, and toalibaba:qwen-image-2.0-proonly when explicitly asked. - Gemini vs OpenAI/Alibaba:
--aspectcurrently works with Gemini only; OpenAI, OpenAI Codex, and Alibaba require--sizeinstead. - OpenAI size support:
openai:passes1K,2K, or4Kto the image tool (only1Kwas checked live).openai-codex:accepts the flag but the backend chooses its own output size (e.g. 1536x1024 for--size 1K).512pxis Gemini-only. - Alibaba size support: All Alibaba Qwen-Image models support
512px,1K, and2K(not4K).
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.
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.
- 28d ago Changed · +7 lines f3752b3cdf8e
- 1mo ago First seen · 301 lines · 56 tokens per session scan A 3ad7f9eaebef
imagine is a skill published in the GitHub repository tallesborges/zdx (20 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 3,934 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…