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/export-jsonschema)<a href="https://agentmods.dev/commands/edochi/mdvs/export-jsonschema"><img src="https://agentmods.dev/badge/commands/edochi/mdvs/export-jsonschema/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/export-jsonschema"><img src="https://agentmods.dev/badge/commands/edochi/mdvs/export-jsonschema.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.00734 |
| Opus 5.5 | $0.00000 | $0.00294 |
| Sonnet 5.5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
export-jsonschema 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
export-jsonschema
Translate mdvs.toml's [fields] block into a JSON Schema 2020-12 document.
Usage
mdvs export-jsonschema [path] [flags]
Flags
| Flag | Default | Description |
|---|---|---|
path |
. |
Directory containing mdvs.toml |
--format json|toml |
json |
Output format. toml produces a TOML serialization of the same JSON Schema |
--output-file FILE |
(stdout) | Write to a file instead of stdout |
Global flags (-o, -v, --logs) are described in
Configuration.
What it does
export-jsonschema reads mdvs.toml, takes the [fields] block, and
translates it into a JSON Schema 2020-12 document. Field types, constraints,
path-scoping, and preprocessor stages are all preserved. The output is a valid
JSON Schema that any standards-compliant validator can consume.
Build configuration ([embedding_model], [chunking], [search]) and scan
settings are not included — JSON Schema only describes the field contract.
Round-tripping with init
export-jsonschema and init --from-jsonschema are designed to round-trip
losslessly:
mdvs export-jsonschema ./project --output-file fields.json
mdvs init ./reborn --from-jsonschema fields.json
The new mdvs.toml reproduces the original [[fields.field]] definitions:
- Field types (strict —
StringisString, not a permissive set) - Constraints (
categories,min/max,min_length/max_length,pattern) - Path-scoping (
allowed,required) - Preprocessor arrays (
preprocess = ["coerce-to-string"], etc.) - The
[fields].ignorelist
mdvs-specific metadata that JSON Schema 2020-12 doesn't model is carried in
x-mdvs.* extension keys; generic JSON Schema validators ignore them, and
init --from-jsonschema reads them back.
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 · 92 lines · 0 tokens per session scan A 238b438c8e20
export-jsonschema 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 734 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.