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 kensaurus/cursor-kenji --skill enhance-web-redesigngit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/enhance-web-redesign)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/enhance-web-redesign"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/enhance-web-redesign/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/kensaurus/cursor-kenji/enhance-web-redesign"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/enhance-web-redesign.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.00058 | $0.03992 |
| Opus 5 | $0.00029 | $0.01996 |
| Sonnet 5 | $0.00012 | $0.00798 |
| Haiku 4.5 | $0.00006 | $0.00399 |
Grade A, and why
enhance-web-redesign 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 5d 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
86% identical to redesign-existing-projects — 61 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Surface router:
/uiux. You are here:enhance-web-redesign. Native iOS/Android (SwiftUI / Compose, no web layer) is out of scope — use Apple HIG / Material directly.
Redesign Skill
Degree of freedom: MIXED. Taste and audit judgment [HIGH freedom]; keep-the-stack, no-break-functionality [LOW freedom — run exactly].
How to reason
- Scan — framework, styling, current patterns
- Triage — AI-tells first (3+ = slop; kill those)
- Fix — existing stack, Fix Priority order; no rewrite
- Preserve — flows still work; deps exist before import
Worked example
Scan: Vite + Tailwind v4; Inter everywhere; three equal feature cards; no hover. Triage: Inter, purple hero gradient, three cards, "Welcome to…" — four tells. Fix: Geist; one accent; asymmetric feature row; hover/active; keep routes. Preserve:
npm run buildgreen; no new framework.
Self-critique before reporting
- Same stack — no framework or styling-library migration
- Tells killed — Phase 0 fingerprints actually gone, not restyled in place
- States exist — hover/focus/loading/empty/error present
- Right owner — one-page polish →
enhance-web-ui; plan-only slop →plan-antislop; greenfield →design-frontend
How This Works
When applied to an existing project, follow this sequence:
- Scan — Read the codebase. Identify the framework, styling method (Tailwind, vanilla CSS, styled-components, etc.), and current design patterns.
- Diagnose — Run through the audit below. List every generic pattern, weak point, and missing state you find.
- Fix — Apply targeted upgrades working with the existing stack. Do not rewrite from scratch. Improve what's there.
Phase 0: 60-Second AI-Tell Triage [HIGH freedom]
Before the full audit, scan for the highest-signal "AI-generated look" fingerprints. If you spot 3+, the page reads as slop and these are the fastest wins. (Distilled from anti-slop research — see anti-slop-ui and taste-skill.)
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.
- 5d ago First seen · 226 lines · 58 tokens per session scan A cbc175b49796
enhance-web-redesign is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 11d ago), licensed MIT. It adds 58 tokens to every session and 3,992 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to redesign-existing-projects, differing in 61 lines, and is treated as a copy.
Other skills, from other repositories
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…
accessibility-audit
Conduct accessibility audits against WCAG 2.2 guidelines. Evaluate pages, components, and flows for conformance at A, AA, and AAA levels. Identify issues, assess severity, provide code fixes, and generate audit reports. Covers automated testing, manual testing, keyboard navigation, screen reader compatibility, color…
Responsive Layout Reviewer
Reviews HTML/CSS or component code for responsive design issues across mobile, tablet, and desktop breakpoints.
design-to-component-translator
Converts Figma/design specifications into production-ready UI components with accurate spacing, typography, color tokens, responsive rules, and interaction states (hover, focus, disabled, active). Generates Tailwind/shadcn code with design system tokens mapping. Use when translating "Figma to code", "design specs to…
responsive-design-system
Implements responsive design systems with mobile-first breakpoints, container queries, fluid typography, and adaptive layouts using Tailwind CSS. Use when users request "responsive design", "mobile-first", "breakpoints", "fluid typography", or "adaptive layout".