vahtian: Skill for Claude Code

.claude/skills/vahtian-ux-auditor/SKILL.md

vahtian-ux-auditor is a skill for Claude Code from heidihelena/vahtian. It costs 113 tokens per session (923 once invoked), scanned A, original, Apache-2.0.

A review process for checking whether Vahtian web pages are easy to understand and use. Vahtian is the website or product being reviewed.

In plain words
What is it for?
Auditing landing pages, product pages, carousels, onboarding flows, and documentation for clarity, accessibility, mobile readability, and clear calls to action.
Why use it?
It finds places where visitors may not understand the page, navigation, choices, or next action. The review uses rendered desktop and mobile screenshots rather than source code alone.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

This is heidihelena/vahtian's own configuration. It tells Claude Code how to work on vahtian itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vahtian configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node .claude/skills/run-vahtian/driver.mjs / # or any path.

Reuse

Borrowing it

Nothing to install: this file belongs to heidihelena/vahtian. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/heidihelena/vahtian/main/.claude/skills/vahtian-ux-auditor/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/heidihelena/vahtian

Made for: Claude Code.

Wrote 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.

agentmods badge for vahtian-ux-auditor

README.md
[![agentmods](https://agentmods.dev/badge/skills/heidihelena/vahtian/vahtian-ux-auditor/github.svg)](https://agentmods.dev/skills/heidihelena/vahtian/vahtian-ux-auditor)
Your own site
<a href="https://agentmods.dev/skills/heidihelena/vahtian/vahtian-ux-auditor"><img src="https://agentmods.dev/badge/skills/heidihelena/vahtian/vahtian-ux-auditor/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.

agentmods 80×15 button for vahtian-ux-auditor

Your own site · 80×15
<a href="https://agentmods.dev/skills/heidihelena/vahtian/vahtian-ux-auditor"><img src="https://agentmods.dev/badge/skills/heidihelena/vahtian/vahtian-ux-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 113 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 923 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00113 $0.00923
Opus 5 $0.00056 $0.00462
Sonnet 5 $0.00023 $0.00185
Haiku 4.5 $0.00011 $0.00092

Measured 12d ago against content hash c358f54aba1b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

vahtian-ux-auditor 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 12d 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.

.claude/skills/vahtian-ux-auditor/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Vahtian UX auditor

Your job is to find the highest-impact comprehension and decision-path problems on a Vahtian page — and only that. You diagnose; you don't implement (that's vahtian-frontend-implementer) and you don't bless wording (that's vahtian-brand-safety).

See the page before you judge it. Don't audit from HTML source. Render it:

node .claude/skills/run-vahtian/driver.mjs /        # or any path

Then open .claude/skills/run-vahtian/shots/<slug>.desktop.png and <slug>.mobile.png. A UX finding you can't point to in a screenshot isn't real.

The one rule

Every UX improvement must make the human decision path clearer. Polish is never the goal; comprehension is. No visual polish before message clarity.

The 10-second test — answer these from the first screen alone

A first-time researcher should be able to answer, without scrolling:

  • What is this?
  • Who is it for?
  • What problem does it solve?
  • What should I click first?
  • Which product should I use?
  • What does the agent do? What does the human decide?
  • What is local / private? What is free? What is institutional?

For each: can they answer it in ≤10s? If not, that's a finding. Rank findings by how many researchers hit them × how badly it blocks the decision.

Review checklist

  • Can a first-time researcher understand the site in 10 seconds?
  • Is the first CTA obvious and singular (not three equal-weight buttons)?
  • Is the product ladder scannable — uniform cards, one CTA each?
  • Is the "Which Vahti should I use?" chooser visible and quick to parse?
  • Is the agentic workflow credible and bounded (says what the agent may do and what only the human decides)?
  • Are the safety invariants (local-first, human-first, audit trail, "does not decide truth") visible, not buried?
  • Does the mobile layout work — readable line length, tap targets, no horizontal scroll, hero legible at 390px?
  • Do the a11y semantics hold — heading order, descriptive links, buttons distinguishable from body links? (Diagnose only; the fix-side rules live in vahtian-frontend-implementer.)
  • Is the page still static, fast, and tracker-free?

Read the full file on GitHub · 84 lines

Changes

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.

  1. 12d ago First seen · 84 lines · 113 tokens per session scan A c358f54aba1b

Subscribe to this mod's changes

vahtian-ux-auditor is a skill published in the GitHub repository heidihelena/vahtian (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 113 tokens to every session and 923 once invoked, about $0.0006 per session on Opus 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-08-31.

Related

Other skills, from other repositories