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/update)<a href="https://agentmods.dev/commands/edochi/mdvs/update"><img src="https://agentmods.dev/badge/commands/edochi/mdvs/update/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/update"><img src="https://agentmods.dev/badge/commands/edochi/mdvs/update.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.01583 |
| Opus 5.5 | $0.00000 | $0.00633 |
| Sonnet 5.5 | $0.00000 | $0.00317 |
| Haiku 4.5 | $0.00000 | $0.00158 |
Grade A, and why
update 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
update
Re-scan files, infer new fields, and update the schema.
Usage
mdvs update [path] [--dry-run]
mdvs update [path] reinfer [fields..] [flags]
Flags
| Flag | Default | Description |
|---|---|---|
path |
. |
Directory containing mdvs.toml |
--dry-run |
Preview changes without writing anything |
Global flags (-o, -v, --logs) are described in
Configuration.
What it does
update re-scans the directory using the existing [scan] config, infers types
and path patterns from the current files, and merges the results into
mdvs.toml. Unlike init, it preserves all existing configuration —
only the [fields] section changes.
Default mode
By default, update only discovers new fields — fields that appear in
frontmatter but aren't yet in mdvs.toml (either as [[fields.field]] entries
or in the ignore list). Existing fields are protected: their types,
allowed/required patterns, nullable flags, and constraints don't change.
Fields that disappear (no longer in any file) are kept in mdvs.toml by
default. This is conservative — removing a field from the schema is an explicit
action.
reinfer subcommand
Re-infer field definitions from scratch. This is a subcommand of update with
its own flags:
| Flag | Description |
|---|---|
fields.. |
Fields to reinfer (all if none specified) |
--with <kinds> |
Comma-separated constraint kinds to apply (categorical, range, none). Requires named fields. |
--max-categories <N> |
Override max distinct values for categorical inference |
--min-repetition <N> |
Override min average repetition for categorical inference |
--dry-run |
Preview changes without writing anything |
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 · 185 lines · 0 tokens per session scan A c124505594a6
update 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 1,583 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.