product-image

product-image is a command for Claude Code from lorena-bordonaba-pau/product-studio. It costs 35 tokens per session (527 once invoked), scanned A, original, MIT.

A command for creating sets of product photographs from real product photos or a store URL. It follows a product-photography workflow and can produce three or five shots in selected visual styles.

In plain words
What is it for?
Preparing product images for online shops, social feeds, stories, or websites in minimalist, elegant, or user-generated-content styles.
Why use it?
It organizes source-image checking, product identification, brand review, shot planning, and product-fidelity checks into one process.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; names the AskUserQuestion tool.

Part of the product-studio plugin — 1 skill, 3 commands shipped together

Good fit Preparing product images for online shops, social feeds, stories, or websites in minimalist, elegant, or user-generated-content styles.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/lorena-bordonaba-pau/product-studio/product-image
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.

Clone the repo
git clone --depth 1 https://github.com/lorena-bordonaba-pau/product-studio

Made for: Claude Code.

Or install product-studio, the plugin that ships this one along with the rest of its 1 skill, 3 commands.

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 product-image

README.md
[![agentmods](https://agentmods.dev/badge/commands/lorena-bordonaba-pau/product-studio/product-image/github.svg)](https://agentmods.dev/commands/lorena-bordonaba-pau/product-studio/product-image)
Your own site
<a href="https://agentmods.dev/commands/lorena-bordonaba-pau/product-studio/product-image"><img src="https://agentmods.dev/badge/commands/lorena-bordonaba-pau/product-studio/product-image/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.

agentmods 80×15 button for product-image

Your own site · 80×15
<a href="https://agentmods.dev/commands/lorena-bordonaba-pau/product-studio/product-image"><img src="https://agentmods.dev/badge/commands/lorena-bordonaba-pau/product-studio/product-image.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 527 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00035 $0.00527
Opus 5 $0.00017 $0.00264
Sonnet 5 $0.00007 $0.00105
Haiku 4.5 $0.00003 $0.00053

Measured 9d ago against content hash 62a3eb14bbc8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

product-image 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 9d 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.

commands/product-image.md · 31 lines

How it starts

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

/product-image — Professional product photography

Generates a set of professional product photos from the user's real photos. Always reply in the user's language.

Source provided by the user: $ARGUMENTS (If empty, ask whether they have a photo folder or their store's URL.)

Instructions

Follow the full flow defined in the product-photography skill (the product-studio plugin's SKILL.md), section "Workflow: images". In short, skipping none:

  1. Check the user's config (~/.claude/product-studio/config.json); if missing, walk them through /product-setup first.
  2. Get the source images (local folder, or URL extraction + quick brand analysis — see references/store-analysis.md) and confirm the detected products.
  3. Build the strict inventory of each product by reading its photos — only what is clearly visible.
  4. Ask in ONE AskUserQuestion: style (minimalist / elegant / UGC — see references/styles.md), quantity (3 or 5) and destination/format (ecommerce, feed, stories, web — see references/shot-plans.md).
  5. Load the company's session template (sessions/<company>.md) or draft one brand-matched to the client and confirm it with the user before generating — all photos for one brand share per-shot settings, light, palette and format.
  6. Check the category-adaptive shot plan (references/shot-plans.md) and the local learnings (~/.claude/product-studio/learnings.md).
  7. Generate image-to-image with the configured provider (references/providers.md), always using the original photo as reference (the one whose angle best matches the shot), with realistic photographic prompts (references/styles.md).
  8. Run the consistency QA on every image against the inventory, the session template AND the AI-artifact checklist; fix mismatches (max 3 attempts) and record the learnings.
  9. Deliver to output/<product>/ with a final summary of what was generated and verified.

Remember the non-negotiable principle: total product fidelity. Never invent or elaborate on what can't be seen; never silently deliver an image that isn't identical to the real product.

Read the full file on GitHub · 31 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. 9d ago First seen · 31 lines · 35 tokens per session scan A 62a3eb14bbc8

Subscribe to this mod's changes

product-image is a command published in the GitHub repository lorena-bordonaba-pau/product-studio (6 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 527 once invoked, about $0.0002 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.