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/modulesgit 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.00013 | $0.01279 |
| Opus 5 | $0.00006 | $0.00639 |
| Sonnet 5 | $0.00003 | $0.00256 |
| Haiku 4.5 | $0.00001 | $0.00128 |
Grade A, and why
modules 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mdvdb modules
Inspect and run the built-in modules that materialize computed frontmatter fields declared in .markdownvdb.schema.yml.
| Module ID | Owns | Execution order |
|---|---|---|
formula |
Formula fields calculated from the current document |
First |
lookup_rollup |
Lookup fields copied from related documents and Rollup aggregations |
Second |
Both modules are always on during ingest, watch updates, and schema changes. modules run is the explicit recomputation surface.
Usage
mdvdb modules <COMMAND> [OPTIONS]
| Command | Description |
|---|---|
list |
List compiled-in modules, versions, and hooks |
validate <MODULE> |
Validate a Formula or Rollup expression without changing files or the index |
run <MODULE> |
Recompute persisted derived data |
status <MODULE> |
Read cached diagnostics without running expressions |
Valid module IDs are formula and lookup_rollup.
List modules
mdvdb modules list
mdvdb modules list --json
JSON output is an array of descriptors:
[
{
"id": "formula",
"name": "Formula",
"version": 1,
"always_on": true,
"hooks": ["full_ingest", "files_changed", "schema_changed", "manual_run"]
},
{
"id": "lookup_rollup",
"name": "Lookup & Rollup",
"version": 1,
"always_on": true,
"hooks": ["full_ingest", "files_changed", "schema_changed", "manual_run"]
}
]
Validate an expression
mdvdb modules validate <MODULE> \
--formula <EXPRESSION> \
--result-type <TYPE>
Supported result types are string, number, boolean, date, datetime, list, and json. Use the formula module for a document Formula and lookup_rollup for a Rollup expression, where values is the reserved input list.
# Formula expression
mdvdb modules validate formula \
--formula 'price * quantity' \
--result-type number
# Rollup expression
mdvdb modules validate lookup_rollup \
--formula 'values.reduce((sum, value) => sum + Number(value), 0)' \
--result-type number \
--json
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 · 198 lines · 13 tokens per session scan A 33720e96e417
modules is a command published in the GitHub repository geckse/markdown-vdb (23 stars, last pushed 18d ago), licensed MIT. It adds 13 tokens to every session and 1,279 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.