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 karon-hyppolite/agent-skills --skill web-design-guidelinesgit clone --depth 1 https://github.com/karon-hyppolite/agent-skillsWrote 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/karon-hyppolite/agent-skills/web-design-guidelines)<a href="https://agentmods.dev/skills/karon-hyppolite/agent-skills/web-design-guidelines"><img src="https://agentmods.dev/badge/skills/karon-hyppolite/agent-skills/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/karon-hyppolite/agent-skills/web-design-guidelines"><img src="https://agentmods.dev/badge/skills/karon-hyppolite/agent-skills/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.00044 | $0.00268 |
| Opus 5 | $0.00022 | $0.00134 |
| Sonnet 5 | $0.00009 | $0.00054 |
| Haiku 4.5 | $0.00004 | $0.00027 |
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 10d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 10d ago First seen · 40 lines · 44 tokens per session scan A f4647ca866a3
web-design-guidelines is a skill published in the GitHub repository karon-hyppolite/agent-skills (4 stars, last pushed 6mo ago), with no licence file. It adds 44 tokens to every session and 268 once invoked, about $0.0002 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
idea-superpowers-suite
Use when running the full idea workflow: capture a rough idea, expand it into design/UI/implementation docs, research similar products, and generate build-ready Markdown artifacts.
idea-to-design-doc
Use when turning a rough idea into a focused product/design Markdown doc through guided questions, without moving into implementation too early.
idea-to-ui-design-brief
Use when turning a product/design doc into a focused UI design brief, optional AI image-generation concept prompts, and implementation-ready UI direction without replacing the main idea workflow.
one-design-language
Constrains UI work to the shared design token vocabulary. Use when creating or modifying any component — new CSS values local to one screen are forbidden; every visual decision comes from the existing tokens (spacing, radii, colors, type scale) in globals.css.
accessibility
Use when building or reviewing web UIs for accessibility — WCAG 2.2 Level AA compliance, semantic HTML over ARIA, keyboard navigation, color contrast, screen reader patterns, and testing approach.
solid-principles
Use when designing classes or APIs to evaluate SOLID compliance — SRP, OCP, LSP, ISP, DIP. Covers what each principle means, how to diagnose violations by symptom, and how to refactor.