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 skills add HermeticOrmus/LibreUIUX-Claude-Code --skill verify-libreuiuxgit 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/skills/hermeticormus/libreuiux-claude-code/verify-libreuiux)<a href="https://agentmods.dev/skills/hermeticormus/libreuiux-claude-code/verify-libreuiux"><img src="https://agentmods.dev/badge/skills/hermeticormus/libreuiux-claude-code/verify-libreuiux/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/skills/hermeticormus/libreuiux-claude-code/verify-libreuiux"><img src="https://agentmods.dev/badge/skills/hermeticormus/libreuiux-claude-code/verify-libreuiux.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.00085 | $0.01461 |
| Opus 5.5 | $0.00034 | $0.00584 |
| Sonnet 5.5 | $0.00017 | $0.00292 |
| Haiku 4.5 | $0.00009 | $0.00146 |
Grade A, and why
verify-libreuiux 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 11d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- verify-libre-embed — 91% identical, 25 lines differ
- verify-libre-secops — 91% identical, 25 lines differ
- verify-design-mastery — 88% identical, 22 lines differ
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify LibreUIUX-Claude-Code
LibreUIUX-Claude-Code is a plugin library, not a running app: 71 plugins under plugins/, published as the libreuiux marketplace. Its user surface is the install. A user adds this repo as a plugin marketplace in Claude Code or Grok Build, installs plugins from it (or runs ./setup.sh from a clone), and then uses the skills, commands, agents and hooks those plugins bring. This skill drives that path in throwaway configs, so a proof never touches your own Claude Code config or Grok home.
Helper (executable, bash; needs claude, grok, jq and git): .grok/skills/verify-libreuiux/bin/control-libreuiux
B=.grok/skills/verify-libreuiux/bin/control-libreuiux
$B --help
$B doctor # worth driving? CLIs, head, manifests in sync
$B run # every plugins, both CLIs, prove each loaded; one JSON result
$B run --only design-mastery # the same for the plugins a change touched
$B run --pr 12 --expect <sha> # the same on a PR head, fetched into a scratch clone
$B install --claude --only design-mastery # a fresh run that keeps its clean config for the next steps
$B details design-mastery # component inventory in the latest run (both CLIs)
$B setup --list # ./setup.sh inside the latest run's clean configs
$B check # scripts/check.sh, the repo's one check command
$B cleanup # drop every run's scratch; the evidence stays
JSON on stdout, progress on stderr, exit 1 on any failed proof. Everything the helper writes lives under VERIFY_LIBREUIUX_HOME (default ~/.local/share/verify-libreuiux): runs/<stamp>-<head8>/ (or <stamp>-pr<N>-<head8>) holds scratch/ and evidence/, and runs/latest points at the newest run.
Launch
- There is no server. Launching is starting a run: a run folder with an empty Claude Code config (
CLAUDE_CONFIG_DIR) and an empty Grok home (GROK_HOME), both underscratch/. - The tree under test is the checkout the helper sits in. With
--pr Nit is a scratch clone ofrefs/pull/N/headfetched fromorigin, and--expect <sha>refuses any other head. - Claude Code adds the tree as the
libreuiuxmarketplace and installs<plugin>@libreuiux. Grok adds the checkout as a marketplace named after its folder, then installs<plugin>@<folder>. - Ready when the marketplace add exits 0:
evidence/claude-marketplace-add.logandevidence/grok-marketplace-add.log(orgrok-install.log) end inexit 0. - Teardown:
runremoves its own scratch when it finishes. Afterinstall, runcleanupwhen you are done withdetailsandsetup.
What ships with it
6 files beside SKILL.md 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.
- 11d ago First seen · 76 lines · 85 tokens per session scan A b94a0f9087f2
verify-libreuiux is a skill published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (115 stars, last pushed 11d ago), licensed MIT. It adds 85 tokens to every session and 1,461 once invoked, about $0.0003 per session on Opus 5.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-10-05.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
verification-loop
A comprehensive verification system for Claude Code sessions. Use when verifying a Claude Code session's work before claiming it is complete.
cli-eval
Create and run evaluation suites, watch live benchmark progress, view scorecards, compare model performance, and integrate eval runs with CI workflows from the CLI.
model-merging
Merge multiple fine-tuned models using mergekit to combine capabilities without retraining. Use when creating specialized models by blending domain-specific expertise (math + coding + chat), improving performance beyond single models, or experimenting rapidly with model variants. Covers SLERP, TIES-Merging, DARE, Task…
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.