get

A command for inspecting one Markdown document in an indexed collection. It shows the document's frontmatter, calculated fields, file details, content hash, and optional links to related documents.

In plain words
What is it for?
Use it to inspect a document, verify calculated values such as an invoice total, view file size and timestamps, or resolve its references and reverse references in machine-readable JSON.
Why use it?
It helps you check what the index knows about a file and diagnose missing or incorrect metadata without opening the document manually.

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/get
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 1,022 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.01022
Opus 5 $0.00008 $0.00511
Sonnet 5 $0.00003 $0.00204
Haiku 4.5 $0.00002 $0.00102

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

Security

Grade A, and why

get 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/get.md · 122 lines

How it starts

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

mdvdb get

Retrieve index metadata for one Markdown document. The command reports its frontmatter, computed values and diagnostics, chunk count, file size, content hash, and timestamps.

Usage

mdvdb get [OPTIONS] <FILE_PATH>
Name Required Description
<FILE_PATH> Yes Project-relative path as stored in the index
--populate No Resolve frontmatter relations and reverse references, one level deep

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

Examples

# Inspect metadata
mdvdb get docs/api.md

# Include resolved relation targets and documents that reference this file
mdvdb get invoices/invoice-104.md --populate

# Machine-readable output
mdvdb get invoices/invoice-104.md --populate --json

JSON output

{
  "path": "invoices/invoice-104.md",
  "content_hash": "a1b2c3d4e5f67890...",
  "frontmatter": {
    "title": "Invoice 104",
    "client": "[[clients/acme]]",
    "price": 120,
    "quantity": 2,
    "total": 240
  },
  "computed_fields": {
    "total": 240
  },
  "computed_field_errors": {},
  "chunk_count": 3,
  "file_size": 712,
  "indexed_at": 1770000100,
  "modified_at": 1770000000,
  "relations": {
    "client": [
      {
        "raw": "[[clients/acme]]",
        "path": "clients/acme.md",
        "exists": true,
        "title": "Acme",
        "frontmatter": {
          "title": "Acme",
          "domain": "acme.example"
        }
      }
    ]
  },
  "referenced_by": [
    {
      "source": "payments/payment-104.md",
      "field": "invoice",
      "title": "Payment 104"
    }
  ]
}

Fields

Field Type Description
path string Project-relative document path
content_hash string SHA-256 hash used for change detection
frontmatter object | null Parsed, materialized YAML frontmatter; authoritative value surface
computed_fields object Successful Formula, Lookup, and Rollup values mirrored for provenance
computed_field_errors object Diagnostics keyed by computed field name
chunk_count number Number of indexed text chunks
file_size number File size in bytes
indexed_at number Unix timestamp of the last ingest
modified_at number | null Filesystem modification timestamp
relations object Resolved frontmatter relations; present only with --populate
referenced_by array Reverse frontmatter references; present only with --populate

Read the full file on GitHub · 122 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 · 122 lines · 15 tokens per session scan A 9502d19116a5

Subscribe to this mod's changes

get 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 1,022 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.