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 agentmods add skills/kensaurus/cursor-kenji/design-mobile-firstnpx skills add kensaurus/cursor-kenji --skill design-mobile-firstgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/design-mobile-first)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/design-mobile-first"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/design-mobile-first.svg" alt="Measured on agentmods" 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.00049 | $0.03431 |
| Opus 5 | $0.00024 | $0.01716 |
| Sonnet 5 | $0.00010 | $0.00686 |
| Haiku 4.5 | $0.00005 | $0.00343 |
Grade A, and why
design-mobile-first 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 2d 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 — 507 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile-First Design Skill
Degree of freedom: MIXED. Pattern choice [HIGH freedom]; breakpoint,
viewport, and existing-hook inventory [LOW freedom — run exactly].
Build interfaces that work on mobile first, then enhance for larger screens.
Not this skill: a desktop that is a linearized phone (no max-width, stacked
at 1440, stretched buttons). That is audit-responsive.
How to reason
- Survey — breakpoints, viewport, existing mobile hooks
- Base — mobile styles first (44px, safe-area)
- Enhance —
sm:/md:/lg:add up; they do not replace the base - Device-check — real phone, not only a resized desktop window
Worked example
Survey: Tailwind
sm/md/lgexist; checkout CTA ish-8; nosafe-area-inset-bottom. Base:min-h-[44px],pb-[env(safe-area-inset-bottom)], stacked fields, 16px inputs. Enhance: two-column names atsm:; table replaces cards atmd:. Device-check: thumb reaches the CTA; iOS does not zoom on focus.
Self-critique before reporting
- Base is mobile — primary layout is not
lg:-only - 44px + safe-area — tap targets and notches were measured
- Real device — not emulator-or-resize only
- Right owner — linearized 1440 desktop →
audit-responsive; hybrid native chrome →enhance-capacitor-ui
CRITICAL: Check Existing First [LOW freedom — run exactly]
Before ANY mobile optimization, verify:
- Check existing breakpoints:
cat tailwind.config.* | grep -A10 "screens\|breakpoints"
rg "sm:|md:|lg:|xl:" --type tsx | head -20
- Check for existing mobile patterns:
rg "useMediaQuery|useBreakpoint|isMobile" --type ts --type tsx
ls -la src/hooks/use*Mobile* src/hooks/use*Responsive* 2>/dev/null
- Check viewport meta:
rg "viewport" src/app/layout.tsx index.html
Why: Maintain consistent responsive patterns across the app.
Mobile-First Principles [HIGH freedom]
1. Design for Mobile First
/* Base styles = mobile */
.card {
padding: 1rem;
font-size: 0.875rem;
}
/* Then enhance for larger screens */
@media (min-width: 640px) {
.card {
padding: 1.5rem;
font-size: 1rem;
}
}
/* Tailwind design-mobile-first */
<div className="p-4 sm:p-6 md:p-8">
<div className="text-sm sm:text-base lg:text-lg">
<div className="grid-cols-1 sm:grid-cols-2 lg:grid-cols-3">
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.
- 2d ago First seen · 507 lines · 49 tokens per session scan A e29a98c71a61
design-mobile-first is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 8d ago), licensed MIT. It adds 49 tokens to every session and 3,431 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-09-03.
Other skills, from other repositories
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…
accessibility-audit
Conduct accessibility audits against WCAG 2.2 guidelines. Evaluate pages, components, and flows for conformance at A, AA, and AAA levels. Identify issues, assess severity, provide code fixes, and generate audit reports. Covers automated testing, manual testing, keyboard navigation, screen reader compatibility, color…
Responsive Layout Reviewer
Reviews HTML/CSS or component code for responsive design issues across mobile, tablet, and desktop breakpoints.
design-to-component-translator
Converts Figma/design specifications into production-ready UI components with accurate spacing, typography, color tokens, responsive rules, and interaction states (hover, focus, disabled, active). Generates Tailwind/shadcn code with design system tokens mapping. Use when translating "Figma to code", "design specs to…
responsive-design-system
Implements responsive design systems with mobile-first breakpoints, container queries, fluid typography, and adaptive layouts using Tailwind CSS. Use when users request "responsive design", "mobile-first", "breakpoints", "fluid typography", or "adaptive layout".