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 agentmods add commands/erhangundogan/videre/fix-datesgit clone --depth 1 https://github.com/erhangundogan/videreWrote 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/erhangundogan/videre/fix-dates)<a href="https://agentmods.dev/commands/erhangundogan/videre/fix-dates"><img src="https://agentmods.dev/badge/commands/erhangundogan/videre/fix-dates.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.01478 |
| Opus 5 | $0.00006 | $0.00739 |
| Sonnet 5 | $0.00003 | $0.00296 |
| Haiku 4.5 | $0.00001 | $0.00148 |
Grade A, and why
fix-dates 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 3d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sets each file's modification time from its EXIF date, so photos sort by when they were taken rather than when they were last copied.
:::danger[This is the only command that changes your files]
There is no undo. Once a file's original modification time is overwritten, it is
gone unless you have a backup. It asks for confirmation first, and --dry-run
shows exactly what it would do.
:::
videre fix-dates --dry-run # show what would change, touch nothing
videre fix-dates # apply (asks for confirmation first)
videre fix-dates --yes # apply without asking (for scripts)
videre fix-dates --silent # no per-file output
videre fix-dates --db ~/photos.db # use a specific database
Why you would want this
Copying, syncing, restoring from backup, or exporting from a photo app all
rewrite a file's modification time to now. A folder of holiday photos ends up
all dated the day you copied them, and every tool that sorts by date, from ls
to Finder to your file manager, shows them in the wrong order.
The date the camera recorded is still there, in EXIF, untouched by any of that. This copies it onto the file itself.
videre scan ~/Photos # read the EXIF dates
videre fix-dates --dry-run # see what would change
videre fix-dates # apply
Exactly what changes
Changed: the file's modification time (mtime), and only that.
Not changed:
| File contents | Never read or rewritten. Only the timestamp metadata is set |
Access time (atime) |
Left as it was |
| Creation / birth time | Not touched. See the platform notes below |
| Filename, path, permissions | Untouched |
| The database | Not updated by this command; run videre prune to re-sync modified_at |
Sub-second precision is set to zero, since EXIF dates have one-second
resolution. A file whose mtime was 10:31:07.482 becomes 10:31:07.000.
Which files are affected
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.
- 3d ago First seen · 152 lines · 13 tokens per session scan A 9b5b16a0e345
fix-dates is a command published in the GitHub repository erhangundogan/videre (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,478 once invoked, about $0.0001 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 commands, from other repositories
deslop
Check the diff against main, and remove all AI generated slop introduced in this branch.
contrib
Profile how top GitHub contributors work — ingest, build personas, and synthesise a capability model + learnable playbook.
memory-init
Initialize local memory store + vector index for this project.
graph
Generate an interactive visual graph of your memories. Powered by graphify (github.com/safishamsi/graphify, MIT).
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.