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 aiappsgbb/awesome-gbb --skill web-experience-designgit clone --depth 1 https://github.com/aiappsgbb/awesome-gbbWrote 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/aiappsgbb/awesome-gbb/web-experience-design)<a href="https://agentmods.dev/skills/aiappsgbb/awesome-gbb/web-experience-design"><img src="https://agentmods.dev/badge/skills/aiappsgbb/awesome-gbb/web-experience-design/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/aiappsgbb/awesome-gbb/web-experience-design"><img src="https://agentmods.dev/badge/skills/aiappsgbb/awesome-gbb/web-experience-design.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.00153 | $0.01962 |
| Opus 5.5 | $0.00061 | $0.00785 |
| Sonnet 5.5 | $0.00031 | $0.00392 |
| Haiku 4.5 | $0.00015 | $0.00196 |
Grade A, and why
web-experience-design 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 6d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Experience Design
Make the next useful action obvious, the important content understandable, and the detail easy to retrieve. A complete document is not automatically a usable interface. Attractive screenshots are not evidence of a working experience.
Merged source; release pending: output acceptance and cross-runtime discovery remain pending; see validation boundaries.
Choose the scope
Identify the target, task and write boundary before changing anything. Reuse the brief, existing design system, approved decisions and repository conventions. Ask only material unanswered questions, one at a time through the available question tool. Do not restart discovery or ask for arbitrary taste preferences.
| Request | Path |
|---|---|
| Audit or plan only | Inspect and propose; do not fix, install or publish. |
| Small refinement | Preserve structure, behavior and brand; state the local intent, make the bounded change, verify affected paths. No full redesign workshop. |
| New experience or structural redesign | Complete the workflow below; obtain direction approval before substantial implementation. |
Choose the primary visitor task: understand, decide, operate, find, act, or present. Mixed experiences may use different modes in different views. These are routing hints, not templates. Load only the relevant part of architecture.
1. Establish content and a baseline
Read the real material before choosing a layout. Record the reader's questions, required content, evidence, consequential caveats, actions and delivery constraints. Separate facts, interpretation and proposed copy. Never invent claims, sources, testimonials, prices, user research or customer results to fill a composition.
Draft interface copy from those facts, not from generic product language. Before
direction approval, run the interface copy pass in craft:
headlines, labels, cards, empty states, errors and alt text in the user's language,
applying gbb-humanizer short-copy guidance where installed. Keep operational UI
terse; preserve facts, sources, technical names and copy the user already approved.
What ships with it
9 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.
- 6d ago Changed · +7 lines c98ecad5ddf8
- 27d ago Changed 3dcfa62622d1
- 1mo ago First seen · 171 lines · 153 tokens per session scan A fde260366f34
web-experience-design is a skill published in the GitHub repository aiappsgbb/awesome-gbb (8 stars, last pushed yesterday), licensed MIT. It adds 153 tokens to every session and 1,962 once invoked, about $0.0006 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-09-22.
Other skills, from other repositories
anti-slop-design
Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.
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 $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
open-design-setup
Prepare or repair a project's prototyping environment so open-design can build prototypes with the project's own component library and render them through the project's toolchain. Use when the library target is needed and docs/design/prototyping.md is missing, stale, or failing; excludes HTML-only design work and…
frontend-visual-qa
Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone. Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI…