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/check)<a href="https://agentmods.dev/commands/edochi/mdvs/check"><img src="https://agentmods.dev/badge/commands/edochi/mdvs/check/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/check"><img src="https://agentmods.dev/badge/commands/edochi/mdvs/check.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.01488 |
| Opus 5.5 | $0.00000 | $0.00595 |
| Sonnet 5.5 | $0.00000 | $0.00298 |
| Haiku 4.5 | $0.00000 | $0.00149 |
Grade A, and why
check 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
check
Validate frontmatter against the schema.
Usage
mdvs check [path]
Flags
| Flag | Default | Description |
|---|---|---|
path |
. |
Directory containing mdvs.toml |
--no-update |
Skip auto-update before validating | |
--jsonschema PATH |
Override the [fields] block of mdvs.toml with an external JSON Schema file (.json or .toml) for this run only |
Global flags (-o, -v, --logs) are described in
Configuration.
What it does
check reads mdvs.toml, scans every markdown file, and validates each field
value against the declared constraints.
By default, check auto-updates the schema before validating (see
[check].auto_update). Use --no-update to skip
the update pass and validate against the committed mdvs.toml as-is — what you
want in CI.
It reports seven kinds of violations:
WrongType— value doesn't match the declaredtype(or fails apatternregex)Disallowed— field appears in a file whose path doesn't match anyallowedglobMissingRequired— file matches arequiredglob but the field is absentNullNotAllowed— field isnullbutnullable = falseInvalidCategory— value is not in the field's declaredcategories(see Constraints)OutOfRange— numeric value violatesmin/max, or length violatesmin_length/max_lengthFrontmatterUnrepresentable— file's YAML can't be represented as JSON (NaN/inf, non-string keys, non-object top-level)
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 · 166 lines · 0 tokens per session scan A 33de06446023
check 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,488 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
landing-publish
Use this command to publish landing pages to the seite site as pages.
publish-draft
Publish a draft article from content/ by removing the draft: true flag, building the site, and optionally deploying.
recall
Recall past Claude Code, Codex, and Cursor sessions about a topic and return a decision-focused brief.
setup
Guided session-recall setup — language, embedder, optional team mode.
prompts
Work with MCP prompt templates for memory operations.
slop-chop
Clean AI writing tells from a file or pasted text with slop-chop.