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 prasad-vennam/Awesome-Android-AI-Agent-Skills --skill android-adaptive-layoutsgit clone --depth 1 https://github.com/prasad-vennam/Awesome-Android-AI-Agent-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/prasad-vennam/awesome-android-ai-agent-skills/android-adaptive-layouts)<a href="https://agentmods.dev/skills/prasad-vennam/awesome-android-ai-agent-skills/android-adaptive-layouts"><img src="https://agentmods.dev/badge/skills/prasad-vennam/awesome-android-ai-agent-skills/android-adaptive-layouts/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/prasad-vennam/awesome-android-ai-agent-skills/android-adaptive-layouts"><img src="https://agentmods.dev/badge/skills/prasad-vennam/awesome-android-ai-agent-skills/android-adaptive-layouts.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.00026 | $0.00892 |
| Opus 5 | $0.00013 | $0.00446 |
| Sonnet 5 | $0.00005 | $0.00178 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
android-adaptive-layouts 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 12d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Android Adaptive Layouts 📱💻💻
Professional strategies for building flexible, responsive Android applications that scale beautifully from phones to tablets and foldables.
⚡ When to Use
- Multi-Device Support: Designing a UI that works on all screen sizes.
- Foldable Support: Adapting layout based on hinge position (Tabletop mode).
- Tablet Optimization: Using extra screen space for "List-Detail" or complex dashboards.
- ChromeOS Support: Adapting for resizable desktop-style windows.
- Dynamic Orientation: Handling rotations without losing state.
🏗️ The 3 Window Size Classes
- Compact (Phone): 0-599dp width. Single column.
- Medium (Small Tablet/Large Phone): 600-839dp width. Navigation rail or multi-pane.
- Expanded (Large Tablet/Desktop): 840dp+ width. Fixed navigation drawer or complex dashboards.
🛠️ Canonical Layouts (Google Standard)
1. List-Detail
- Compact: Shows list, then navigate to detail screen.
- Expanded: Side-by-side list and detail (always visible).
2. Supporting Pane
- Expanded: Central work area with a persistent tool or info pane beside it.
3. Feed/Grid
- Compact: 1-2 columns.
- Expanded: 4-6 columns with responsive grid margins.
🚀 Adaptive Layout Tools
1. WindowSizeClass (Material 3)
- Benefit: Automatically categorizes the current window size.
- Use Case: Decide which UI to show based on
calculateWindowSizeClass().
2. TwoPaneLayout (Foldable Support)
- Benefit: Automatically handles display on single-screen vs dual-screen/foldable devices.
- Rule: Give content weights (e.g., list = 1, detail = 2).
📐 Layout Execution Best Practices
- Responsive Grid: Use
FlowRowandFlowColumnfor wrapping content automatically. - Dynamic Margins: Use larger horizontal margins (e.g., 24dp or 32dp) for wider screens.
- Modal Bottom Sheets: Convert
ModalBottomSheet(Phone) intoNavigationDrawerorModalNavigationDrawer(Tablet). - Fixed Content Width: For text content, avoid full-screen width on tablets (Keep it between 400dp and 600dp for readability).
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.
- 12d ago First seen · 81 lines · 26 tokens per session scan A 41862b039a19
android-adaptive-layouts is a skill published in the GitHub repository prasad-vennam/Awesome-Android-AI-Agent-Skills (9 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 892 once invoked, about $0.0001 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
animate-expo
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and…
leanback-to-compose-tv-migration
Provides instructions and architectural patterns for migrating Android TV applications from legacy Leanback UI Toolkit, Android Views, or Support Fragments to Jetpack Compose for TV (androidx.tv). Use this skill for Leanback to Compose migrations, including browse screen, settings screen, authentication screen, login…
maui-data-binding
Guidance for .NET MAUI XAML and C# data bindings — compiled bindings, INotifyPropertyChanged / ObservableObject, value converters, binding modes, multi-binding, relative bindings, fallbacks, and MVVM best practices. USE FOR: setting up compiled bindings with x:DataType, implementing INotifyPropertyChanged or…
expo-brownfield
Framework (OSS). Integrate Expo and React Native into an existing native iOS or Android app. Use for brownfield, embedding a React Native screen in SwiftUI/UIKit or Kotlin, or AAR/XCFramework packaging. Covers isolated and integrated approaches. For building or distributing a purely native app with EAS, use…
migrate-xml-views-to-jetpack-compose
Provides a structured workflow for migrating an Android XML View to Jetpack Compose. This skill details the step-by-step process, from planning and dependency setup, to theming and layout migration, validation and XML cleanup. Use this skill when you need to migrate an XML View to Jetpack Compose in an Android…
web-haptics
Add haptic feedback to web apps using the web-haptics library. Use when building mobile-facing UIs that need tactile feedback on buttons, toggles, forms, pickers, and other interactive elements.