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/shapediver/AppBuilderSdkWrote 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/shapediver/appbuildersdk/mobile-fallback)<a href="https://agentmods.dev/rules/shapediver/appbuildersdk/mobile-fallback"><img src="https://agentmods.dev/badge/rules/shapediver/appbuildersdk/mobile-fallback/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/shapediver/appbuildersdk/mobile-fallback"><img src="https://agentmods.dev/badge/rules/shapediver/appbuildersdk/mobile-fallback.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.00272 |
| Opus 5.5 | $0.00000 | $0.00109 |
| Sonnet 5.5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
mobile-fallback 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 7d 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
Mobile fallback
Theme is the general default. This is independent of AppShell vs grid.
- Containers:
AppBuilderTemplateSelector.defaultProps.mobileFallbacksandmobileBreakpoint. - Anchors:
ViewportAnchor2d/ViewportAnchor3ddefaultProps.mobileFallback. An anchor theme may set its ownmobileBreakpoint.
JSON overlays the defined fields of a single container or anchor. Omitted JSON keeps the theme. Omitted JSON and theme keep the previous behavior.
Applied below TemplateSelector mobileBreakpoint (default "md"). AppShell navbarBreakpoint defaults to the same value.
disabledhides the content and does not move it. Otherwise the content moves.- A move is one hop of the original content. Content that arrived from somewhere else does not move again.
- Merge uses the additional container's
positionandorder. Omittedposition/ordermeans append.
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.
- 7d ago First seen · 26 lines · 0 tokens per session scan A dfcb412cd302
mobile-fallback is a cursor rule published in the GitHub repository shapediver/AppBuilderSdk (15 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 272 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-10-15.
Other cursor rules, from other repositories
chakra-ui-best-practices
A set of rules for building React interfaces with Chakra UI, a component library for styled and accessible user interfaces. It covers themes, responsive layouts, accessibility, performance, and reusable components.
nextjs-react-tailwind-cursorrules-prompt-file
Cursor rules for Next.js development with React and Tailwind CSS integration.
react-components-creation-cursorrules-prompt-file
Cursor rules for React component creation and development.
react-chakra-ui-cursorrules-prompt-file
Cursor rules for React development with Chakra UI integration.
react-styled-components-cursorrules-prompt-file
Cursor rules for React development with Styled Components integration.
react-chakra-ui---folder-structure
A standard folder layout for React and Chakra UI projects, including separate locations for components, pages, themes, hooks, utilities, and assets. It also defines how Chakra UI theme files are grouped.