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.
npx skills add ouestcharlie/ouestcharlie-woof --skill sort-enrich-photos-stravagit clone --depth 1 https://github.com/ouestcharlie/ouestcharlie-woofWrote 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/ouestcharlie/ouestcharlie-woof/sort-enrich-photos-strava)<a href="https://agentmods.dev/skills/ouestcharlie/ouestcharlie-woof/sort-enrich-photos-strava"><img src="https://agentmods.dev/badge/skills/ouestcharlie/ouestcharlie-woof/sort-enrich-photos-strava/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/ouestcharlie/ouestcharlie-woof/sort-enrich-photos-strava"><img src="https://agentmods.dev/badge/skills/ouestcharlie/ouestcharlie-woof/sort-enrich-photos-strava.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00134 | $0.02119 |
| Opus 5 | $0.00067 | $0.01059 |
| Sonnet 5 | $0.00027 | $0.00424 |
| Haiku 4.5 | $0.00013 | $0.00212 |
Grade A, and why
sort-enrich-photos-strava 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 12d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sorting photos against an activity log
The log knows what they did and when; photos carry timestamps. That's enough to file and caption with almost no human input — which is what makes it worth automating, and what makes it dangerous: a wrong rule moves hundreds of files confidently.
So: propose a complete plan, get approval, execute, verify.
This covers what the log can explain, typically ~15% of a camera roll. The rest
is the sort-enrich-photos-interactive-clusters skill.
Conventions come from the library
No settings file. Tunable knobs and per-run decisions live in
scripts/sort_photos.py — read it before filling it in; the comments explain
each field.
Everything else comes from looking at the library:
- Copy the folder layout already in use. Don't assume a shape — it might be
<year>/<date>_<place>/,Events/<name>/, or a flat pile. The script takes a literal relative path of any depth, so any layout works. Sample a few places; conventions drift over years. - Read the tag facets before inventing a tag. This is how you avoid
Climbingnext to an establishedRockClimbing.
Nothing to copy — empty library, first sort — means proposing two or three concrete shapes with examples and confirming once. It's the hardest decision to undo: a thousand files under a disliked scheme is a thousand files to move again.
Near-duplicate tags accumulate: Oliv beside Olivier, an accented and
unaccented spelling. The tell is a pair differing by case, accent or prefix with
lopsided counts — the rare one is usually the mistake. Ask which is canonical,
then retag the smaller set rather than remembering an alias. A correction in a
config file must be re-read forever; one applied to the photos is simply true.
The library can't go stale. A settings file records what someone believed the conventions were; the folders and tags record what they are.
1. Index and size up
Index the staging partition, get a count and date range, and also list the folder directly — the index and filesystem disagree in informative ways.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 197 lines · 134 tokens per session scan A ca1221973d9c
sort-enrich-photos-strava is a skill published in the GitHub repository ouestcharlie/ouestcharlie-woof (8 stars, last pushed 2d ago), licensed MIT. It adds 134 tokens to every session and 2,119 once invoked, about $0.0007 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…