organize-by-resolution

organize-by-resolution is a command for Claude Code from danielrosehill/Claude-Image-Production-Plugin. It costs 0 tokens per session (545 once invoked), scanned A, original, MIT.

An image-organizing command that places pictures into folders based on their pixel resolution, from tiny and standard-definition images up to 8K.

In plain words
What is it for?
Use it to scan a folder, assign resolution categories, show counts and proposed changes, and organize files after confirmation.
Why use it?
It helps separate images by likely display or print quality instead of leaving different sizes mixed together.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the image-production plugin — 29 skills, 19 commands shipped together

Good fit Use it to scan a folder, assign resolution categories, show counts and proposed changes, and organize files after confirmation.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/danielrosehill/claude-image-production-plugin/organize-by-resolution
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/danielrosehill/Claude-Image-Production-Plugin

Made for: Claude Code.

Or install image-production, the plugin that ships this one along with the rest of its 29 skills, 19 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 organize-by-resolution

README.md
[![agentmods](https://agentmods.dev/badge/commands/danielrosehill/claude-image-production-plugin/organize-by-resolution/github.svg)](https://agentmods.dev/commands/danielrosehill/claude-image-production-plugin/organize-by-resolution)
Your own site
<a href="https://agentmods.dev/commands/danielrosehill/claude-image-production-plugin/organize-by-resolution"><img src="https://agentmods.dev/badge/commands/danielrosehill/claude-image-production-plugin/organize-by-resolution/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 organize-by-resolution

Your own site · 80×15
<a href="https://agentmods.dev/commands/danielrosehill/claude-image-production-plugin/organize-by-resolution"><img src="https://agentmods.dev/badge/commands/danielrosehill/claude-image-production-plugin/organize-by-resolution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 545 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.00000 $0.00545
Opus 5 $0.00000 $0.00272
Sonnet 5 $0.00000 $0.00109
Haiku 4.5 $0.00000 $0.00055

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

Security

Grade A, and why

organize-by-resolution 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.

commands/organize-by-resolution.md · 40 lines

What it actually says

Organize Images by Resolution

Sort images in the current folder (or a user-specified folder) into resolution-based subfolders.

Task

  1. Ask which folder to operate on — default is the current working directory. Confirm recursion: descend into subfolders, or flat only? Default flat.

  2. Probe each image for pixel dimensions. Prefer identify (ImageMagick) for speed; fall back to exiftool for formats it mishandles (HEIC, some RAW):

    identify -format "%w %h %i\n" "*.jpg" "*.png" "*.heic" "*.webp" 2>/dev/null
    # or
    exiftool -s -s -s -ImageWidth -ImageHeight "image.jpg"
    
  3. Bucket images by the longest edge (so portrait and landscape shots land in the same tier):

    • 8K/ — longest edge ≥ 7680
    • 4K/ — longest edge ≥ 3840 and < 7680
    • 2K/ — longest edge ≥ 2560 and < 3840
    • 1080p-class/ — longest edge ≥ 1920 and < 2560
    • 720p-class/ — longest edge ≥ 1280 and < 1920
    • SD/ — longest edge ≥ 640 and < 1280
    • tiny/ — longest edge < 640
    • other/ — probe failures, non-image files
  4. Preview before acting — print a table of image → bucket with counts per bucket. Do not move anything until the user confirms.

  5. Prefer symlinks or a CSV manifest over physical moves unless the user asks otherwise:

    • Option A: symlinked subfolders (4K/photo.jpg → ../photo.jpg)
    • Option B: metadata/resolution-buckets.csv mapping file → bucket
    • Option C: physical move (only on explicit confirmation)
  6. Log to notes/organize-by-resolution-{timestamp}.md with bucket counts, method chosen (symlink / manifest / move), and any probe failures.

Notes

  • Check identify (from ImageMagick) is installed before using it; otherwise fall back to exiftool.
  • Skip non-image files silently, but list them in the log.
  • For RAW formats (NEF, CR2, ARW, DNG), exiftool is more reliable than identify.
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. 10d ago First seen · 40 lines · 0 tokens per session scan A 572b8d5a53c0

Subscribe to this mod's changes

organize-by-resolution is a command published in the GitHub repository danielrosehill/Claude-Image-Production-Plugin (16 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 545 tokens. 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.