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.
git clone --depth 1 https://github.com/edochi/mdvsWrote 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/edochi/mdvs/clean)<a href="https://agentmods.dev/commands/edochi/mdvs/clean"><img src="https://agentmods.dev/badge/commands/edochi/mdvs/clean/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/commands/edochi/mdvs/clean"><img src="https://agentmods.dev/badge/commands/edochi/mdvs/clean.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.00000 | $0.00742 |
| Opus 5.5 | $0.00000 | $0.00297 |
| Sonnet 5.5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
clean 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 10d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
clean
Delete the search index.
Usage
mdvs clean [path]
Flags
| Flag | Default | Description |
|---|---|---|
path |
. |
Directory containing mdvs.toml |
Global flags (-o, -v, --logs) are described in
Configuration.
What it does
clean deletes the .mdvs/ directory, which contains the Lance dataset that
makes up the search index (plus the cached embedding model). The mdvs.toml
configuration file is never touched — you can rebuild the index at any time with
build.
The command is idempotent — running it when .mdvs/ doesn't exist is a no-op.
It also refuses to delete if .mdvs/ is a symlink, as a safety measure.
Output
Compact (default)
mdvs clean example_kb
Cleaned "example_kb/.mdvs"
┌──────────────────────────┬───────────────────────────────────────────────────┐
│ removed │ true │
├──────────────────────────┼───────────────────────────────────────────────────┤
│ path │ example_kb/.mdvs │
├──────────────────────────┼───────────────────────────────────────────────────┤
│ files removed │ 2 │
├──────────────────────────┼───────────────────────────────────────────────────┤
│ size │ 113.7 KB │
└──────────────────────────┴───────────────────────────────────────────────────┘
When there's nothing to clean:
Nothing to clean — "example_kb/.mdvs" does not exist
┌──────────────────────────┬───────────────────────────────────────────────────┐
│ removed │ false │
├──────────────────────────┼───────────────────────────────────────────────────┤
│ path │ example_kb/.mdvs │
├──────────────────────────┼───────────────────────────────────────────────────┤
│ files removed │ 0 │
├──────────────────────────┼───────────────────────────────────────────────────┤
│ size │ 0 B │
└──────────────────────────┴───────────────────────────────────────────────────┘
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.
- 10d ago First seen · 99 lines · 0 tokens per session scan A a4696475abf2
clean is a command published in the GitHub repository edochi/mdvs (27 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 742 tokens. 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-10-05.
Other commands, from other repositories
create-entity
Create a new entity in the domain model using MDL.
landing-publish
Use this command to publish landing pages to the seite site as pages.
db-migrate.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
setup
Guided session-recall setup — language, embedder, optional team mode.
prompts
Work with MCP prompt templates for memory operations.
fix
System prompt for /fix slash command.