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 Uxcel-Lab/product-skills --skill mobile-responsivenessgit clone --depth 1 https://github.com/Uxcel-Lab/product-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/uxcel-lab/product-skills/mobile-responsiveness)<a href="https://agentmods.dev/skills/uxcel-lab/product-skills/mobile-responsiveness"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/mobile-responsiveness/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/uxcel-lab/product-skills/mobile-responsiveness"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/mobile-responsiveness.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.00092 | $0.02828 |
| Opus 5 | $0.00046 | $0.01414 |
| Sonnet 5 | $0.00018 | $0.00566 |
| Haiku 4.5 | $0.00009 | $0.00283 |
Grade A, and why
ux-mobile-responsiveness-audit 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 11d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Responsiveness Audit Skill
How this skill behaves (read first)
This is an evaluative skill — it reviews existing work against mobile/touch standards, it doesn't generate. Flagging is safe, so it auto-runs and is built to be called as a validation step by generative skills whenever the target is mobile or responsive (the component family, screens, and flows all hand off here for their mobile context).
It owns the mobile/touch-adaptation concern in this repo. To avoid duplicating its sibling audits, it defers:
- WCAG ratios, screen-reader/assistive-tech, keyboard operability, alt text, captions → the accessibility audit. This skill judges physical touch ergonomics and layout adaptation, not AT compatibility or contrast math.
- Visual composition — hierarchy, spacing aesthetics, emphasis → the aesthetics audit.
- Usability, flow, and interaction logic → the heuristics audit.
- Content structure / navigation scheme → the information-architecture audit; type scale →
ux-typography.
Applicability gate: this audit only applies when the target is meant to work on mobile or across breakpoints. If a design is explicitly desktop-only (e.g. a complex internal admin tool with no mobile support), say so and skip — don't manufacture mobile findings.
Scope discipline. When invoked directly (the user named this audit), review only this concern — don't pull in sibling audits. It runs alongside other lenses only when an orchestrator (ux-design-review) or a generative skill calls it under docs/orchestration-policy.md, where it sits in Tier B — offered (only when the platform is mobile). Explicit scope always wins.
What this skill changes vs. default behavior
By default, "is it mobile-friendly?" gets a vague answer — "make the buttons bigger," "it should be responsive" — with no threshold, no severity, and no systematic sweep. This skill forces:
- Every finding names the violated principle (reflow, touch-target size, thumb reach, etc.) and gives the concrete threshold (44pt / 48dp, ≥8dp spacing, ≥16px body).
- Severity rated by whether it blocks the task on the device vs. adds friction vs. polish.
- A specific fix, not "optimize for mobile."
- A systematic sweep of all seven areas, so issues beyond "small tap targets" — orientation locks, wrong keyboard types, gesture dead-ends, non-reflowing layouts — actually get caught.
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.
- 11d ago First seen · 174 lines · 92 tokens per session scan A 5b9099f3d62d
ux-mobile-responsiveness-audit is a skill published in the GitHub repository Uxcel-Lab/product-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 92 tokens to every session and 2,828 once invoked, about $0.0005 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
design-mobile-apps
Use when the user wants to design a mobile app or UI screens, when they mention their Sleek (sleek.design) projects, or when implementing Sleek designs in code (HTML, React Native, SwiftUI).
appllama-app-design-skill
Build native-feeling, benchmark-quality mobile app screens (Expo / React Native). Use when designing or implementing any mobile UI — screens, flows, onboarding, paywalls, tab bars, sheets, settings, empty states — or when polishing motion, navigation, typography, dark mode, or perceived performance. Enforces Apple HIG…
ios-hig-design
Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", "HIG compliance", "SF Symbols", "haptic feedback", "iOS accessibility", "make my app feel native", or "follow Apple design guidelines".…
appllama-app-design-skill
Build native-feeling, benchmark-quality mobile app screens (Expo / React Native). Use when designing or implementing any mobile UI — screens, flows, onboarding, paywalls, tab bars, sheets, settings, empty states — or when polishing motion, navigation, typography, dark mode, or perceived performance. Enforces Apple HIG…
pm-brand-motion
A guided process for defining a brand's motion style and making a logo animation demonstration.
pm-proto
A product-prototyping workflow for planning how an application should work and what its screens should contain. It connects product requirements to interface layouts and interactions.