Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mostafa-drz/claude-skillsnpx agentmods add skills/mostafa-drz/claude-skills/organize-screenshotsWrote 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/mostafa-drz/claude-skills/organize-screenshots)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/organize-screenshots"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/organize-screenshots/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/mostafa-drz/claude-skills/organize-screenshots"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/organize-screenshots.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.00053 | $0.01717 |
| Opus 5.5 | $0.00021 | $0.00687 |
| Sonnet 5.5 | $0.00011 | $0.00343 |
| Haiku 4.5 | $0.00005 | $0.00172 |
Grade A, and why
organize-screenshots 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 1mo 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Organize Screenshots
Scan for recent screenshots, visually classify them, and organize with descriptive names.
Preferences
Read ~/.claude/skills/organize-screenshots/preferences.md using the Read tool. If not found, no preferences are set.
Context
On startup, use Bash to detect: current git branch and count recent screenshots in the source folder (default ~/Desktop). Skip any that fail.
Command routing
Check $ARGUMENTS:
help→ display help then stopconfig→ interactive setup then stopreset→ delete~/.claude/skills/organize-screenshots/preferences.md, confirm, stop- anything else → process screenshots
Flags
Parse from $ARGUMENTS:
--source <dir>— override source folder (default: ~/Desktop or preference)--days <N>— look back N days (default: 3 or preference)--move— move instead of copy--all— skip classification, take everything- Remaining text — target directory
Help
Screenshots — Scan, classify, and organize screenshots
Usage:
/organize-screenshots <target-dir> Scan Desktop, organize into target
/organize-screenshots <target-dir> --source ~/Downloads Scan specific folder
/organize-screenshots <target-dir> --days 1 Only last 24 hours
/organize-screenshots <target-dir> --move Move instead of copy
/organize-screenshots <target-dir> --all Skip classification, take all
/organize-screenshots config Set defaults
/organize-screenshots reset Clear preferences
/organize-screenshots help This help
Examples:
/organize-screenshots ./docs/images
/organize-screenshots ./pr-assets --days 1
/organize-screenshots ~/bug-report --source ~/Downloads --move
What it does:
1. Finds recent screenshots in source folder
2. Visually reviews each one (reads the image)
3. Classifies: relevant to current work or not
4. Suggests descriptive filenames
5. Copies (or moves) to target with new names
Current preferences:
(shown above under Preferences)
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.
- 1mo ago Changed · +3 lines 352e6cb83d6e
- 1mo ago First seen · 210 lines · 53 tokens per session scan A 89125b89cb71
organize-screenshots is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 1,717 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-31.
Other skills, from other repositories
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.
rudder-instrumentation-planning
Designs event taxonomies and instrumentation strategies from business requirements. Use when designing event taxonomy from scratch or restructuring existing instrumentation strategy.
rudder-instrumentation-debugging
Diagnoses and fixes validation errors, schema issues, and instrumentation problems. Use when debugging validation errors, schema issues, or instrumentation problems.
rudder-ai-events-verify
Verifies RudderStack AI events locally: captures what an instrumented app or MCP server sends, validates it against the AI events v0.3 schema, and checks joins, counts, identity and content. Use when testing AI events, or when AI or MCP events look wrong or missing.