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.
git clone --depth 1 https://github.com/blockmatic/basilicWrote 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/rules/blockmatic/basilic/mobile-first)<a href="https://agentmods.dev/rules/blockmatic/basilic/mobile-first"><img src="https://agentmods.dev/badge/rules/blockmatic/basilic/mobile-first/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/rules/blockmatic/basilic/mobile-first"><img src="https://agentmods.dev/badge/rules/blockmatic/basilic/mobile-first.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.00000 | $0.00374 |
| Opus 5.5 | $0.00000 | $0.00150 |
| Sonnet 5.5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
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 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.
What it actually says
Core Principle
Always design/develop mobile-first. Start with mobile styles, enhance for larger screens using Tailwind breakpoints
Tailwind Breakpoints
Mobile-first: Base (no prefix, <640px) → sm: (≥640px) → md: (≥768px) → lg: (≥1024px) → xl: (≥1280px) → 2xl: (≥1536px)
Patterns
Layout: flex flex-col sm:flex-row (column mobile, row desktop)
Typography: text-xl sm:text-2xl md:text-3xl (smaller to larger)
Spacing: p-4 sm:p-6 md:p-8 (smaller to larger)
Visibility: block sm:hidden (mobile-only), hidden sm:block (desktop-only)
Grid: grid grid-cols-1 sm:grid-cols-2 lg:grid-cols-3 (single to multiple columns)
Component Examples
Dialog: w-full h-full sm:w-auto sm:h-auto (fullscreen mobile, centered desktop)
Nav: flex-col sm:flex-row with hamburger (sm:hidden) and horizontal menu (hidden sm:flex)
Testing
Test mobile first (dev tools emulation), verify touch targets (≥44x44px), check text readability, test landscape
Common Mistakes
❌ Desktop-first: flex-row max-md:flex-col
❌ Missing mobile base: lg:flex lg:gap-4
❌ Small touch targets: w-6 h-6 buttons
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 · 31 lines · 0 tokens per session scan A 6ca1d4a6741d
mobile-first is a cursor rule published in the GitHub repository blockmatic/basilic (90 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 374 tokens. 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 cursor rules, from other repositories
nextjs
Next.js with TypeScript and Tailwind UI best practices.
nextjs-tailwind-typescript-apps-cursorrules-prompt
Cursor rules for Next.js development with Tailwind CSS and TypeScript integration.
qwik-tailwind-cursorrules-prompt-file
Cursor rules for Qwik development with Tailwind CSS integration.
hatch3r-design-system-detection
Mandatory detection of existing design tokens, theme primitives, and component library before AI agents author new UI components.
hatch3r-ux-states-and-flows
Four-state surface contract (loading/empty/error/partial), user-flow decomposition before implementation, and microcopy + tone discipline for end-user UIs.
hatch3r-accessibility-standards
Accessibility standards covering WCAG 2.2 AA compliance, keyboard navigation, screen readers, and ARIA patterns.