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/scangit 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/scan)<a href="https://agentmods.dev/commands/erhangundogan/videre/scan"><img src="https://agentmods.dev/badge/commands/erhangundogan/videre/scan.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.02519 |
| Opus 5 | $0.00006 | $0.01260 |
| Sonnet 5 | $0.00003 | $0.00504 |
| Haiku 4.5 | $0.00001 | $0.00252 |
Grade A, and why
scan 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reads a folder recursively and records every supported media file in the database. Run this first: everything else reads from what it creates.
videre scan ~/Photos # scan into the default database
videre scan # same, using the folder from `videre config set path`
videre scan ~/Photos --similar # also fingerprint images/videos for near-duplicate detection
videre scan ~/Photos --db ~/photos.db # write to a specific database instead
videre scan ~/Photos --output # write JSONL to ~/.videre/hashes.jsonl instead of SQLite
videre scan ~/Photos --output out.jsonl # write JSONL to a specific file
videre scan ~/Photos --retry-incomplete # only files an earlier scan didn't finish
videre scan ~/Photos --silent # no progress output
videre scan ~/Photos --json # print one JSON summary object instead
videre scan ~/Photos --type video # only videos
videre scan ~/Photos --ext heic,mov # only these formats
videre scan ~/Photos --path ~/Photos/2024 # only this subfolder
:::tip These filters work the same way across commands, and combine. See scoping a run. :::
Re-running is safe and idempotent, since existing entries are updated in place.
:::note
--output and --db cannot be combined. A bare --output must come after
the folder, or it swallows the folder as its value.
--output-sqlite still works as an alias for --db. It was the original name,
from when JSONL and SQLite were peer output formats rather than one
destination and one opt-out. Existing scripts do not need changing.
:::
What it records
For every file: its content hash, size, timestamps, extension, detected type,
and EXIF where present (date taken, GPS, dimensions). Nothing is opened for
decoding unless you pass --similar.
It does not prepare search or detect faces. Those are
videre embed and videre faces, run
separately and much slower.
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 · 238 lines · 13 tokens per session scan A f0388da63082
scan 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 2,519 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.