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/HermeticOrmus/LibreUIUX-Claude-CodeWrote 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/plugins/hermeticormus/libreuiux-claude-code/data-validation-suite)<a href="https://agentmods.dev/plugins/hermeticormus/libreuiux-claude-code/data-validation-suite"><img src="https://agentmods.dev/badge/plugins/hermeticormus/libreuiux-claude-code/data-validation-suite/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/plugins/hermeticormus/libreuiux-claude-code/data-validation-suite"><img src="https://agentmods.dev/badge/plugins/hermeticormus/libreuiux-claude-code/data-validation-suite.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
data-validation-suite 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 15d 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.
What it actually says
{
"name": "data-validation-suite",
"version": "1.2.0",
"description": "Schema validation, data quality monitoring, streaming validation pipelines, and input validation for backend APIs",
"author": {
"name": "Seth Hobson",
"url": "https://github.com/wshobson"
},
"homepage": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code",
"repository": "https://github.com/HermeticOrmus/LibreUIUX-Claude-Code",
"license": "MIT",
"keywords": [
"validation",
"schema",
"data-quality",
"pydantic",
"jsonschema"
]
}
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 15d ago Changed · -6 lines dc9250e628bc
- 1mo ago First seen · 26 lines scan A 4cee7284ae69
data-validation-suite is a plugin published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (115 stars, last pushed 11d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
data-engineering
ETL pipeline construction, data warehouse design, batch processing workflows, and data-driven feature development.
data-validation-suite
Schema validation, data quality monitoring, streaming validation pipelines, and input validation for backend APIs.
preset-snowflake-cortex-skills
Snowflake Cortex Agent skills for explicit direct Snowflake Cortex REST and SQL workflows only: account and authentication context, agent management, and confirmation-gated agent runs. Requires a Snowflake account; does not use Preset credentials. Do not use for MCP-only work.
open-webui
Open WebUI operator suite — REST API administration (v0.10.x: user/group lifecycle, model catalog GitOps via models/sync, config-as-code, SCIM, event webhooks, the 0.10.0 accesscontrol→accessgrants break, auth traps), RAG pipeline wiring (HuggingFace embedding + reranker via LiteLLM in front of HuggingFace Text Embed.
inference-apis
Inference-API compatibility suite — the three open LLM serving protocols as third-party surfaces: OpenAI Chat Completions + legacy /v1/completions (7 local servers, gateways, 10 cloud compat endpoints, reasoning-field schism, client wire behavior), OpenAI Responses (spec, streaming events, store/previousresponseid se.
litellm
LiteLLM proxy operator suite — multi-pod Redis/Valkey coordination (the silent per-pod-fallback failure mode, the 4-way coordination-Redis resolution order incl. the undocumented generalsettings.coordinationredis block since v1.93.0, Sentinel/Cluster support matrix with fix versions, per-pod-vs-shared truth table wit.