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.
curl -O https://raw.githubusercontent.com/heidihelena/vahtian/main/.claude/skills/vahtian-frontend-implementer/SKILL.mdgit clone --depth 1 https://github.com/heidihelena/vahtianWrote 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/heidihelena/vahtian/vahtian-frontend-implementer)<a href="https://agentmods.dev/skills/heidihelena/vahtian/vahtian-frontend-implementer"><img src="https://agentmods.dev/badge/skills/heidihelena/vahtian/vahtian-frontend-implementer/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/heidihelena/vahtian/vahtian-frontend-implementer"><img src="https://agentmods.dev/badge/skills/heidihelena/vahtian/vahtian-frontend-implementer.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.00095 | $0.00983 |
| Opus 5 | $0.00048 | $0.00491 |
| Sonnet 5 | $0.00019 | $0.00197 |
| Haiku 4.5 | $0.00010 | $0.00098 |
Grade A, and why
vahtian-frontend-implementer 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.
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.
Vahtian frontend implementer
You make the smallest coherent code/content change that fixes a UX issue. You
do not change the product's philosophy, and you do not invent copy that hasn't
passed vahtian-brand-safety.
What this site is (work within it)
- Static HTML, one
index.htmlper product. No framework, no bundler, no build step. Styles are inline<style>blocks; behaviour is small inline<script>. Deployed via Cloudflare (wrangler.jsonc,assets.directory = "."). - Zero external requests — no trackers, no CDN fonts, no analytics. This is a brand invariant, not an accident.
See it before and after
node .claude/skills/run-vahtian/driver.mjs / # render target page(s)
# edit …
node .claude/skills/run-vahtian/driver.mjs / # re-render
node .claude/skills/run-vahtian/driver.mjs --check / /studyvahti /llms.txt # link smoke test
Compare shots/<slug>.desktop.png and shots/<slug>.mobile.png before/after.
Don't claim a fix works until you've looked at both widths.
Rules of engagement
- Smallest coherent change. One issue per edit. No drive-by refactors, no "while I'm here". Don't redesign everything at once.
- Preserve the philosophy. Local-first, human-first / AI-second, audit-ledger,
"does not decide scientific truth" must survive every edit — never trade them
away to simplify. The canonical wording lives in
vahtian-brand-safety; defer to it, don't paraphrase it. - No new dependencies, no framework. Don't add npm packages, web fonts, trackers, analytics, or external scripts. If you think you need one, you probably don't — say why instead of adding it.
- Copy comes from brand-safety. Any user-facing string you add or change must
have passed
vahtian-brand-safety(PASS) first — its tables, not your memory, define what is sayable. - Meet the design language, don't just match surroundings. The bar is
.claude/skills/vahtian-site/references/design-language.md— tokens, component specs, and the taste do/don't list. Reuse existing CSS variables and class names, and read the file's existing<style>before adding rules; when the page and the design language disagree, raise the page to the spec.
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 · 95 tokens per session scan A 707a80ca9fa1
vahtian-frontend-implementer is a skill published in the GitHub repository heidihelena/vahtian (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 95 tokens to every session and 983 once invoked, about $0.0005 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.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
waitlist-page
A simple waitlist page for collecting email addresses from people interested in a new product or early-access release.
tailwindcss
Tailwind CSS v4 conventions — semantic design tokens for theme-safe styling, mobile-first responsive layouts, and v4-first utilities. Use when styling components or writing className utilities with Tailwind. Don't use for plain CSS, CSS-in-JS (styled-components, emotion), or other utility frameworks.