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 phuonghx/aim-cli --skill web-design-guidelinesgit clone --depth 1 https://github.com/phuonghx/aim-cliWrote 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/phuonghx/aim-cli/web-design-guidelines)<a href="https://agentmods.dev/skills/phuonghx/aim-cli/web-design-guidelines"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/web-design-guidelines/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/phuonghx/aim-cli/web-design-guidelines"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/web-design-guidelines.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.00091 | $0.00546 |
| Opus 5.5 | $0.00036 | $0.00218 |
| Sonnet 5.5 | $0.00018 | $0.00109 |
| Haiku 4.5 | $0.00009 | $0.00055 |
Grade A, and why
web-design-guidelines 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 1mo 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Interface Guidelines Audit
This skill reviews UI source against a living checklist of interface best practices and reports what falls short. Because the rules are fetched fresh each run, the audit reflects the most recent published guidance rather than a snapshot frozen into this file.
What it does
Given one or more files (or a glob), it retrieves the current guidelines, reads the target
code, evaluates every applicable rule, and emits concise findings keyed to file:line so
each issue is easy to locate and fix.
Procedure
- Pull the current rules. Fetch the guidelines document from the source below at the start of every review — do not work from memory or a cached copy. The fetched content carries both the rules to apply and the exact output format to follow.
- Gather the targets. Read the files named in the request. If none were given, ask which files or pattern to review before continuing.
- Evaluate. Walk the code against each rule in the fetched guidelines.
- Report. Write findings in the terse
file:lineform the guidelines specify, one issue per line.
Where the rules come from
Retrieve the latest rules before each audit:
https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md
Use a web fetch to load that URL. Treat whatever it returns as the authority for both the checks and the reporting format — it supersedes anything described here.
How this fits a design workflow
Two skills bracket the act of building UI: one informs the design before code exists, this one inspects the result after.
| Phase | Skill | Purpose |
|---|---|---|
| Before coding | frontend-design |
Learn the principles — color, type, spacing, UX |
| After coding | web-design-guidelines (this) |
Audit the implementation for compliance |
1. DESIGN -> absorb the principles
2. BUILD -> implement the interface
3. AUDIT -> run this review <- you are here
4. FIX -> resolve the findings
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.
- 1mo ago First seen · 56 lines · 91 tokens per session scan A 2c4486edb300
web-design-guidelines is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 3mo ago), licensed MIT. It adds 91 tokens to every session and 546 once invoked, about $0.0004 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-03.
Other skills, from other repositories
design-critique
Use this skill to audit an interface that already exists and say precisely why it looks generated, templated, or unfinished — a scored rubric across composition, typography, color, states, accessibility and copy, ending in a ranked fix list. Triggers: user says "review the design", "critique this UI", "why does this…
design-craft
Design or substantially improve user-facing interfaces with a product-specific visual direction, content hierarchy, and rendered critique. Use for new screens, landing pages, redesigns, typography/layout work, or UI that feels generic or AI-generated. For small fixes, preserve the existing design without starting a…
von-restorff-effect
Apply the Von Restorff Effect — the element that differs from its neighbours is the one remembered. Use when a single action must dominate. For overall ordering rather than single-element emphasis, use visual-hierarchy.
handoff-spec
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use design-qa-checklist; for reusable library components use component-spec (design-systems).
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
readable-measure
Set line length and measure for comfortable reading across type sizes and breakpoints. Use when tuning body text. Covers measure only — for the full size and weight scale, use typography-scale.