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/danielrosehill/Claude-Image-Production-PluginWrote 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/danielrosehill/claude-image-production-plugin/organize-by-resolution)<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.
<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>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.00000 | $0.00545 |
| Opus 5.5 | $0.00000 | $0.00218 |
| Sonnet 5.5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00055 |
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 2mo 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
Organize Images by Resolution
Sort images in the current folder (or a user-specified folder) into resolution-based subfolders.
Task
-
Ask which folder to operate on — default is the current working directory. Confirm recursion: descend into subfolders, or flat only? Default flat.
-
Probe each image for pixel dimensions. Prefer
identify(ImageMagick) for speed; fall back toexiftoolfor 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" -
Bucket images by the longest edge (so portrait and landscape shots land in the same tier):
8K/— longest edge ≥ 76804K/— longest edge ≥ 3840 and < 76802K/— longest edge ≥ 2560 and < 38401080p-class/— longest edge ≥ 1920 and < 2560720p-class/— longest edge ≥ 1280 and < 1920SD/— longest edge ≥ 640 and < 1280tiny/— longest edge < 640other/— probe failures, non-image files
-
Preview before acting — print a table of image → bucket with counts per bucket. Do not move anything until the user confirms.
-
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.csvmapping file → bucket - Option C: physical move (only on explicit confirmation)
- Option A: symlinked subfolders (
-
Log to
notes/organize-by-resolution-{timestamp}.mdwith bucket counts, method chosen (symlink / manifest / move), and any probe failures.
Notes
- Check
identify(from ImageMagick) is installed before using it; otherwise fall back toexiftool. - Skip non-image files silently, but list them in the log.
- For RAW formats (NEF, CR2, ARW, DNG),
exiftoolis more reliable thanidentify.
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.
- 2mo ago First seen · 40 lines · 0 tokens per session scan A 572b8d5a53c0
organize-by-resolution is a command published in the GitHub repository danielrosehill/Claude-Image-Production-Plugin (21 stars, last pushed yesterday), 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.
organize-by-resolution compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| organize-by-resolutiondanielrosehill/Claude-Image-Production-Plugin | Command | 21 | yesterday | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |