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/geckse/markdown-vdb/schemagit clone --depth 1 https://github.com/geckse/markdown-vdbWhat 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.00017 | $0.01268 |
| Opus 5 | $0.00009 | $0.00634 |
| Sonnet 5 | $0.00003 | $0.00254 |
| Haiku 4.5 | $0.00002 | $0.00127 |
Grade A, and why
schema 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mdvdb schema
Show the merged metadata schema for indexed Markdown documents. mdvdb infers fields from YAML frontmatter and applies optional definitions from .markdownvdb.schema.yml, including relations and computed fields.
Usage
mdvdb schema [--path <PREFIX> | --shard <ID>] [GLOBAL OPTIONS]
| Flag | Description |
|---|---|
--path <PREFIX> |
Restrict the schema to a relative folder prefix |
--shard <ID> |
Use the folder configured for a named Shard |
--path and --shard conflict. Without either option, the command returns the collection-wide schema. It also accepts all global options.
Examples
mdvdb schema
mdvdb schema --path invoices
mdvdb schema --shard operations
mdvdb schema --path invoices --json
Field types
JSON serializes these names in PascalCase:
| Type | Meaning |
|---|---|
String |
Text value |
Number |
Integer or decimal value |
Boolean |
true or false |
List |
YAML sequence |
Date |
Date-shaped text such as 2026-08-06 |
Mixed |
More than one incompatible observed type |
Relation |
Whole-value reference to another Markdown document |
File |
Reference to a non-Markdown file |
Json |
Structured object or nested collection |
Formula |
Deterministic value calculated from the current document |
Lookup |
Value copied from a related document |
Rollup |
Formula evaluated over values collected from related documents |
Schema overlay
The optional overlay adds annotations, type declarations, relation targets, and computed-field definitions. Global fields apply collection-wide; scopes apply to folder prefixes.
# .markdownvdb.schema.yml
fields:
status:
description: Document lifecycle status
allowed_values: [draft, review, published]
required: true
scopes:
invoices:
fields:
client:
field_type: relation
target: clients
total:
field_type: formula
formula: price * quantity
result_type: number
client_domain:
field_type: lookup
relation_field: client
target_field: domain
related_total:
field_type: rollup
relation_field: related_invoices
target_field: total
formula: values.reduce((sum, value) => sum + Number(value), 0)
result_type: number
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 First seen · 173 lines · 17 tokens per session scan A d3964beff62a
schema is a command published in the GitHub repository geckse/markdown-vdb (23 stars, last pushed 18d ago), licensed MIT. It adds 17 tokens to every session and 1,268 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.
Other commands, from other repositories
fieldtheory
Explain and drive the Field Theory CLI — bookmark-sourced seeds, repo-aware possibility runs that score ideas onto a 2x2 grid, and the interconnected .md files they leave behind. Trigger when the user asks about ft, bookmarks, seeds, ft possible (or the older name ft ideas), grids, dots/nodes, or how to turn saved…
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
q-research
Read the research-mode skill's SKILL.md for the full ruleset before proceeding. Follow all constraints, the source lookup cascade, the token budget, and the "what counts as cited" rules exactly.
ingest-l1
L1 analysis loop for the abapwiki knowledge base: for each batch it launches the abap-analyzer sub-agent in parallel, then the adversarial judge abap-deepcheck (separate session), applies only the analyses that pass the fail-closed gate, and commits. Resumes exactly after an interruption. Use this skill to document…
web-search
Search fetched web-source Markdown by regex and pull surrounding context for the best hits. Optionally restrict to one source alias.
docs-refresh
Re-fetch a cached source, ignoring the 7-day cache. Use when upstream content has changed.