Borrowing it
Nothing to install: this file belongs to erhangundogan/videre. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/erhangundogan/videre/main/CLAUDE.mdgit 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/instructions/erhangundogan/videre/claude-md)<a href="https://agentmods.dev/instructions/erhangundogan/videre/claude-md"><img src="https://agentmods.dev/badge/instructions/erhangundogan/videre/claude-md.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.1 | $0.07993 | $0.07993 |
| Opus 5 | $0.03997 | $0.03997 |
| Sonnet 5 | $0.01599 | $0.01599 |
| Haiku 4.5 | $0.00799 | $0.00799 |
Grade A, and why
videre CLAUDE.md 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 2d 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 — 613 lines — stays where its author put it; the contents beside it link to each section on GitHub.
videre
A fast Rust CLI for managing a local media library: duplicate detection, semantic search, and face recognition, all around a single SQLite database.
User-facing documentation lives at https://docs.videre.sh, generated from
docs/ in this repo. This file is for working on videre, in two parts kept
deliberately separate: the working methodology just below (how to work
here), then the measured facts (build and test invariants, findings, and
traps easy to reintroduce). It is deliberately not a command reference. When you
change behaviour, update the relevant page under docs/src/content/docs/ in the
same commit.
How to work on videre
Methodology, kept separate from the measured facts that follow. These are working practices, not project truths.
Discovery before spec. For any change touching shared logic, several subcommands, cross-cutting arguments or common behaviour, search code, tests, git history and docs exhaustively first. Ask rather than guess.
Shared code first. The same thing implemented twice is the worst outcome; the
second caller triggers extraction and refactoring of the first. Where it lives is
the videre-core-versus-shared-module rule under Project structure.
Test first when fixing a bug. Write it, run it, watch it fail. A test that has never failed has not been shown to test anything.
Find the cause before mitigating. cargo test has four target kinds
(--lib, --bins, --test, --doc), so tests/ is not the set of tests.
Verify before claiming done. Run the command and read its real output; if tests fail, say so with the output.
Challenge inherited constraints. The model, the schema and the stored data are variables. Ask what recompute cost is acceptable before optimising within assumed limits.
Read the docs before advising. Grep videre's own docs for a flag before recommending a value.
New settings go in config.toml and videre config set, never a new
environment variable. Do not design for backwards compatibility; users install
latest.
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.
- 2d ago Changed · +6 lines · +145 tokens per session f747ed0e4560
- 7d ago First seen · 607 lines · 7,848 tokens per session scan A d87a1b8f634a
videre CLAUDE.md is an instructions file published in the GitHub repository erhangundogan/videre (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 7,993 tokens to every session, about $0.0400 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.