image-studio

image-studio is a skill for Claude Code, Codex from flurdy/agent-skills. It costs 35 tokens per session (1,660 once invoked), scanned A, original, MIT.

A workflow for creating, comparing, refining, and exporting image assets such as icons, illustrations, backgrounds, and other raster images from one creative brief.

In plain words
What is it for?
Use it to generate image assets, request variants, refine an image, or ask for a vector icon when the workflow supports it.
Why use it?
It keeps image variations tied to the same brief and makes provider and variant choices explicit before generation.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/flurdy/agent-skills/image-studio
Any agent
npx skills add flurdy/agent-skills --skill image-studio
Clone the repo
git clone --depth 1 https://github.com/flurdy/agent-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for image-studio

README.md
[![agentmods](https://agentmods.dev/badge/skills/flurdy/agent-skills/image-studio.svg)](https://agentmods.dev/skills/flurdy/agent-skills/image-studio)
Your own site
<a href="https://agentmods.dev/skills/flurdy/agent-skills/image-studio"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/image-studio.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,660 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.01660
Opus 5 $0.00017 $0.00830
Sonnet 5 $0.00007 $0.00332
Haiku 4.5 $0.00003 $0.00166

Measured 5d ago against content hash 31b31700d58d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

image-studio scanned grade A with 1 finding 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 5d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

allowed-tools: "Read,Write,Grep,Glob,AskUserQuestion,ToolSearch,Bash(curl:*),Bash(file:*),Bash(mkdir:*),mcp__recraft__*"
skills/image-studio/SKILL.md · 130 lines

How it starts

The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Image Studio

Generate project-ready icons, illustrations, backgrounds, and raster imagery from one creative brief. Use Recraft when it is configured. Other image providers are optional adapters, not a requirement.

Usage

/image-studio "A friendly green leaf icon for an environmental dashboard"
/image-studio icon "A green leaf" --vector
/image-studio illustration "A product onboarding scene" --providers recraft,openai --variants 2
/image-studio refine <image-url> "use a dark background and retain the subject"

Guardrails

  • Do not generate or call a provider until the user has confirmed the provider set and number of variants for this run. Treat provider billing as unknown unless the runtime proves otherwise. An explicit current-run command such as --providers recraft --variants 2 is confirmation; otherwise ask immediately before generation.
  • Never infer that OpenAI, Google, or another provider is configured, available, or free. Use only tools actually available in the current runtime, and do not perform hidden retries or extra generations.
  • Keep one shared brief across providers. State unavoidable provider-specific changes before generating.
  • Do not claim outputs are equivalent. Compare them against the brief, not against each other as a technical benchmark.
  • Do not use third-party logos, characters, or living-artist imitation unless the user confirms they have the necessary rights. Flag uncertainty rather than making a legal claim.
  • Do not alter source code or commit assets unless the user explicitly asks. Do not overwrite an existing asset without confirmation.

1. Build the creative brief

Extract or ask for the minimum missing details:

Field Required guidance
Asset Icon, logo, illustration, background, or photorealistic image
Subject and composition Main subject, must-have and must-avoid details
Destination Product surface and intended path, if known
Format SVG/vector for scalable icons; PNG/WebP/JPEG for raster assets
Size and ratio Pixel dimensions or ratio; request target sizes for raster
Transparency Required, forbidden, or irrelevant
Style Reference, palette, lighting, line weight, and accessibility constraints
Variants Provider set and variants per provider

Read the full file on GitHub · 130 lines

Changes

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.

  1. 5d ago First seen · 130 lines · 35 tokens per session scan A 31b31700d58d

Subscribe to this mod's changes

image-studio is a skill published in the GitHub repository flurdy/agent-skills (7 stars, last pushed 6d ago), licensed MIT. It adds 35 tokens to every session and 1,660 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens