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 kelvinkosbab/AppBootstrapAI --skill android-adaptive-layout-progit clone --depth 1 https://github.com/kelvinkosbab/AppBootstrapAIWrote 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/kelvinkosbab/appbootstrapai/android-adaptive-layout-pro)<a href="https://agentmods.dev/skills/kelvinkosbab/appbootstrapai/android-adaptive-layout-pro"><img src="https://agentmods.dev/badge/skills/kelvinkosbab/appbootstrapai/android-adaptive-layout-pro/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/kelvinkosbab/appbootstrapai/android-adaptive-layout-pro"><img src="https://agentmods.dev/badge/skills/kelvinkosbab/appbootstrapai/android-adaptive-layout-pro.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.00112 | $0.01149 |
| Opus 5.5 | $0.00045 | $0.00460 |
| Sonnet 5.5 | $0.00022 | $0.00230 |
| Haiku 4.5 | $0.00011 | $0.00115 |
Grade A, and why
android-adaptive-layout-pro 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Android code for large-screen and foldable readiness. This is the deep-review companion to the always-on android-large-screen-best-practices.md rule — the rule steers while writing; this skill audits whole screens and the manifest. Report only genuine problems; don't nitpick.
Applies to Jetpack Compose apps (with View-interop notes). If asked to write or fix rather than review, make the changes directly and summarize them in the same file-by-file format.
Review process:
- Audit how layouts branch using
references/size-classes.md— window size class reads, breakpoint API, canonical layouts vs hand-rolled conditionals, content width, navigation components per class. - Audit foldable behavior using
references/foldables.md— posture handling,FoldingFeatureobservation, state survival across fold/unfold and display switches. - Audit configuration, input, and testing using
references/quality-checklist.md— manifest restrictions (Android 16), multi-window assumptions, camera orientation, keyboard/mouse/stylus/drag-and-drop, Play quality-tier readiness, test coverage per size class.
If doing a partial review, load only the relevant reference files.
Core Instructions
- The unit of adaptation is the window, not the device. Any device-type heuristic (
isTablet,smallestScreenWidthDp) is a finding regardless of how well it happens to work today — foldables and multi-window break it. - Assume Android 16 behavior. Orientation/aspect-ratio/resizability restrictions are ignored on ≥ 600dp screens for targetSdk 36+; a locked portrait layout is a bug waiting to ship, not a deliberate constraint. Flag the restriction AND the layout that depended on it.
- Fold/unfold and resize are configuration changes. Trace what happens to user input, scroll position, selection, and in-flight work — state in plain
rememberor Activity fields is a finding. - Prefer the scaffolds. Hand-rolled
if (expanded) Row else Columntrees aren't wrong, but when a Material 3 adaptive scaffold fits (navigation suite, list-detail, supporting pane), recommend it — it handles runtime resizes and back navigation the custom code usually forgets. - Severity by user impact: broken (stretched/unusable layout, state loss on fold, camera preview wrong) > degraded (phone layout made wider, bottom bar on a 13" screen, no hover/keyboard support) > polish (missing large/extra-large tuning).
- Cross-reference, don't duplicate: keyboard focus and a11y semantics belong to
android-accessibility-pro; recomposition cost toandroid-compose-pro.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 66 lines · 112 tokens per session scan A 20ed8e21a778
android-adaptive-layout-pro is a skill published in the GitHub repository kelvinkosbab/AppBootstrapAI (8 stars, last pushed 6d ago), licensed MIT. It adds 112 tokens to every session and 1,149 once invoked, about $0.0004 per session on Opus 5.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
kmp-glassmorphism-ui
Implements a production-grade Glassmorphism design system for Kotlin Multiplatform (KMP) Compose Multiplatform projects. Use when the user asks for glass UI, frosted glass effects, glassmorphism theme, translucent/transparent UI components, liquid/blob animated backgrounds, or premium modern dark-mode design in a…
figma-a11y-annotations
Rules for generating accessibility annotations on iOS/iPadOS mobile designs in Figma. Enforces a bare-minimum annotation discipline, an iOS vocabulary instead of web ARIA terms, and exact grammar for names, control types, page titles, values, hints, headings, groups, and reading order. Never annotates visible text as…
iOS SwiftUI Accessibility
Enforces WCAG 2.2 accessible coding patterns when writing SwiftUI — labels, traits, Dynamic Type, contrast, touch targets, focus management, orientation, and more. Based on the ios-swiftui-accessibility-techniques project with 41 static analysis rules across 24 WCAG criteria.
compose-component-design
Use when designing or reviewing reusable Jetpack Compose component APIs with modifier parameters, root layout placement, caller-provided variable content, primitive content parameters, optional content, or boolean shape flags.
maui-accessibility
Improve MAUI accessibility. USE FOR: semantic labels, hints, headings, screen-reader focus/announcements, AutomationProperties, touch targets, decorative content, TalkBack/VoiceOver/Narrator checks. DO NOT USE FOR: general layout, automation-only tests, performance.
compose-screens-footguns
Compose screen and interaction traps: navigation, adaptive layout, window insets, pagers, toolbars, sheets, list drag and selection, sliders, text fields, settings UI, one-shot effects. Use when layout, gestures or navigation misbehave.