info

A command that reports statistics and synchronization status for a Markdown document collection. It also estimates the work needed to rebuild the search index, which is the data structure used to find documents.

In plain words
What is it for?
Use it to inspect a whole collection, folder, or configured shard and view file, chunk, vector, edge, and reindex counts, including machine-readable JSON output.
Why use it?
It shows whether files on disk and the index agree, and reveals the likely cost of reindexing before you start it.

Command

Install

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.

agentmods
npx agentmods add commands/geckse/markdown-vdb/info
Clone the repo
git clone --depth 1 https://github.com/geckse/markdown-vdb
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 813 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00813
Opus 5 $0.00008 $0.00407
Sonnet 5 $0.00003 $0.00163
Haiku 4.5 $0.00002 $0.00081

Measured 2d ago against content hash d33ebfc006d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

info 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.

docs/cli/commands/info.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

mdvdb info

Show statistics for the whole collection, a folder, or a configured Shard. The command compares Markdown files on disk with the current index and estimates the work required to reindex the selected scope.

Usage

mdvdb info [OPTIONS] [PATH]

Arguments and options

Name Default Description
[PATH] . Relative folder to inspect
--shard <ID> Inspect the folder configured for a named Shard; conflicts with PATH

The command also accepts all global options, including --json and --root.

Examples

# Whole collection
mdvdb info

# One folder
mdvdb info docs

# One named Shard
mdvdb info --shard research

# Machine-readable output
mdvdb info docs --json

Reported values

Field Description
file_count Markdown files discovered on disk in the scope
indexed_file_count Indexed files in the scope
chunk_count Indexed chunks in the scope
vector_count Whole collection: measured vector count; scoped view: chunk plus edge vectors attributed to the scope
edge_count Edge vectors whose source file is in scope
reindex_chunks Chunks a full reindex of the scope would produce
reindex_estimated_tokens Estimated embedding input tokens
reindex_estimated_api_calls Estimated provider calls using the configured batch size
sync Counts of new, changed, unchanged, and deleted files
index_file_size Size of the complete index file, even for a scoped report
embedding Provider, model, and dimensions recorded by the index
last_updated Unix timestamp of the last index save

JSON output

{
  "scope": "docs/",
  "is_whole_vault": false,
  "file_count": 42,
  "indexed_file_count": 41,
  "chunk_count": 184,
  "vector_count": 197,
  "edge_count": 13,
  "reindex_chunks": 191,
  "reindex_estimated_tokens": 68320,
  "reindex_estimated_api_calls": 2,
  "index_file_size": 12345678,
  "embedding": {
    "provider": "OpenAI",
    "model": "text-embedding-3-small",
    "dimensions": 1536
  },
  "sync": {
    "new": 1,
    "changed": 1,
    "unchanged": 40,
    "deleted": 0
  },
  "last_updated": 1770000000
}

Read the full file on GitHub · 103 lines

Changes

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.

  1. 2d ago First seen · 103 lines · 15 tokens per session scan A d33ebfc006d8

Subscribe to this mod's changes

info is a command published in the GitHub repository geckse/markdown-vdb (23 stars, last pushed 18d ago), licensed MIT. It adds 15 tokens to every session and 813 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-30.

Related

Other commands, from other repositories