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 lenar-amirov/product-pipeline-public --skill ui-pattern-librarygit clone --depth 1 https://github.com/lenar-amirov/product-pipeline-publicWrote 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/lenar-amirov/product-pipeline-public/ui-pattern-library)<a href="https://agentmods.dev/skills/lenar-amirov/product-pipeline-public/ui-pattern-library"><img src="https://agentmods.dev/badge/skills/lenar-amirov/product-pipeline-public/ui-pattern-library/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/lenar-amirov/product-pipeline-public/ui-pattern-library"><img src="https://agentmods.dev/badge/skills/lenar-amirov/product-pipeline-public/ui-pattern-library.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.00075 | $0.00528 |
| Opus 5.5 | $0.00030 | $0.00211 |
| Sonnet 5.5 | $0.00015 | $0.00106 |
| Haiku 4.5 | $0.00007 | $0.00053 |
Grade A, and why
ui-pattern-library 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 2mo 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Patterns for Solution Sketches
Serves the /sketch job: turn a solution hypothesis into concrete screens.
The question is never "which component is prettiest" — it's "which
pattern delivers the mechanism this hypothesis promises".
Method
- Start from the hypothesis mechanism. Read the solution hypothesis
(
output/solution-hypotheses.md, linked ids in the registry): the "Formula: if X then Y because Z" line names the mechanism. The pattern must implement Z — everything else is decoration. - Pick a pattern per mechanism, e.g.:
- reduce effort at a step → inline editing, smart defaults, one-tap confirm, progressive disclosure
- build trust → social proof blocks, transparent pricing breakdown, recognizable payment affordances
- create/capture intent → save-for-later, wishlists, follow/subscribe, re-engagement entry points
- explain something new → empty states that teach, contextual tooltips, first-run checklists (NOT tours nobody reads)
- surface at the right moment → contextual banners/sheets anchored to the user's current task, not global modals
- Respect platform conventions the segment already knows (CONTEXT.md: platform). A familiar mediocre pattern usually beats a novel one — the novelty tax is real and shows up in concept tests.
- Name the risk per screen — what the concept test (step 8.5) should probe: discoverability? comprehension? trust?
Output — into output/solution-sketch.md
Per screen: purpose (which hypothesis/mechanism) → chosen pattern + why → elements list top-to-bottom → user flow in/out → open risk for testing. Text wireframes are fine; Figma via MCP when connected.
Anti-patterns
- Design-system lectures (tokens, atomic design, component APIs) — that's the design team's domain, not a PM sketch.
- Patterns chosen by taste with no link to the hypothesis mechanism.
- Novel interactions where a platform convention exists — unless novelty IS the hypothesis.
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.
- 2mo ago First seen · 48 lines · 75 tokens per session scan A 0aba44098c78
ui-pattern-library is a skill published in the GitHub repository lenar-amirov/product-pipeline-public (11 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 528 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
ux-product-auditor
Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a severity. Use this to review an interface, diagnose low conversion or activation, find where users drop off, get structured product feedback, or decide which UX fixes to…
interface-craft
Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or…
presentation-design
Designs slide decks and one-pagers that carry an argument rather than decorate one — deck structure, headlines that state the takeaway, charts that make a single point, and the different rules board decks and conference talks follow. Use this to build or fix a pitch deck, board deck, or conference talk, to design a…
visual-content
Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the generation prompts where they are AI-produced. Use this to turn a written piece into a visual format, design a carousel or infographic, create social graphics, or fix visuals…
brand-identity
Defines and applies visual brand — logo usage, palette, typography, imagery direction, and the guidelines that keep expression consistent across product and marketing surfaces. Use this to establish a brand from scratch, audit whether an existing brand is being applied consistently, build brand guidelines, or decide…
design-styles
Applies a deliberate visual direction to an interface — minimalist editorial, industrial utilitarian, or high-polish commercial — each with its own type scale, palette behavior, surface treatment, and motion. Use this when a product needs a point of view rather than defaults, when choosing between visual directions…