Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/klh/speedy-claudenpx agentmods add skills/klh/speedy-claude/klh-lit-devWrote 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/klh/speedy-claude/klh-lit-dev)<a href="https://agentmods.dev/skills/klh/speedy-claude/klh-lit-dev"><img src="https://agentmods.dev/badge/skills/klh/speedy-claude/klh-lit-dev/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/klh/speedy-claude/klh-lit-dev"><img src="https://agentmods.dev/badge/skills/klh/speedy-claude/klh-lit-dev.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.00050 | $0.06159 |
| Opus 5 | $0.00025 | $0.03080 |
| Sonnet 5 | $0.00010 | $0.01232 |
| Haiku 4.5 | $0.00005 | $0.00616 |
Grade A, and why
klh-lit-dev 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 4d 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.
This is a copy
88% identical to lit-dev — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 971 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lit Web Components
Part of klh/skills — personal agent skills by Klaus L. Hougesen. Install:
npx skills add klh/skills --skill klh-lit-dev
Tech Stack
| Tool | Purpose | Version |
|---|---|---|
| Lit | Web component library | Latest (lit) |
| TypeScript | Type-safe development | Latest |
| Zod | Schema validation & type inference | Latest |
| Playwright | E2E/component testing | Latest (@playwright/test) |
| ESLint | Linting | Latest with Lit configs |
| Turborepo | Monorepo build system | Latest |
| pnpm | Package management | Latest (strict peer dependencies) |
Setup commands:
pnpm create turbo@latest # or pnpm init
pnpm add lit zod @playwright/test
pnpm add -D typescript @types/node eslint eslint-plugin-lit
Overview
Lit is a lightweight library (~5KB) for building fast, standards-based web components. At its core: reactive state, scoped styles, and declarative templates via tagged template literals.
Core principle: Every Lit component is a standard web component—interoperable across any framework or vanilla HTML.
When to Use
- When creating Lit web components with TypeScript decorators, JSDoc documentation, Zod validation, and Playwright testing
- When building reusable web components, design systems, or shareable UI elements that work across frameworks
Component Structure Pattern
Follow this 7-point pattern for every Lit component:
components/
my-component/
my-component.ts # Component definition
my-component.zod.ts # Zod schemas + TS types
my-component.spec.tsx # Playwright tests
fixtures/
basic.html # Fixture for testing
interactive.html
index.ts # Barrel export
index.ts # Root barrel export
What ships with it
2 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.
- 4d ago First seen · 971 lines · 50 tokens per session scan A 74439704cd42
klh-lit-dev is a skill published in the GitHub repository klh/speedy-claude (11 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 6,159 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to lit-dev, differing in 16 lines, and is treated as a copy.
Other skills, from other repositories
image-compare
Compare two image files on disk and report what changed, region by region. Trigger on "what changed between these two images", "diff these PNGs", "did this render drift", "compare screenshots/exports/renders".
visual-qa-testing
Visually QA a web application by launching it in Cursor's built-in browser, taking screenshots, checking console errors, and auditing network requests. Use after making UI changes to verify they look correct.
review-screenshot
A standard workflow for taking screenshots to check a user interface, using a dedicated review process for different verification modes.
visual-regression-lab
Compare captures; stitch lazy/animated pages.
visual-qa-vision-agent
Equips the AI agent with visual QA capabilities using Playwright/Puppeteer and the agent's innate Vision capabilities to self-correct UI layout, CSS alignment, and visual regressions.
visual-qa
Use when verifying that a UI renders correctly. Covers visual regression testing, responsive checks across breakpoints, cross-browser verification, and screenshot-based review of an implementation against a design.