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 GDvega/super-android-kotlin-firebase-skill --skill context-aware-ui-designgit clone --depth 1 https://github.com/GDvega/super-android-kotlin-firebase-skillWrote 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/gdvega/super-android-kotlin-firebase-skill/context-aware-ui-design)<a href="https://agentmods.dev/skills/gdvega/super-android-kotlin-firebase-skill/context-aware-ui-design"><img src="https://agentmods.dev/badge/skills/gdvega/super-android-kotlin-firebase-skill/context-aware-ui-design/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/gdvega/super-android-kotlin-firebase-skill/context-aware-ui-design"><img src="https://agentmods.dev/badge/skills/gdvega/super-android-kotlin-firebase-skill/context-aware-ui-design.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.00039 | $0.00903 |
| Opus 5.5 | $0.00016 | $0.00361 |
| Sonnet 5.5 | $0.00008 | $0.00181 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade A, and why
context-aware-ui-design 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Design Android UI according to the app context, not generic aesthetics.
When to use
- Designing or improving an Android screen after build/tests have passed.
- Choosing UI structure for a domain such as health, finance, education, productivity, maps or social features.
- Reviewing an AI-generated app for context mismatch, unclear hierarchy or risky interaction design.
- Adapting Compose UI for sensitive data, older adults, outdoor use, low connectivity or multi-device workflows.
Inputs to inspect
- Gate result from
design-test-gate. - App domain, target user, primary journey and business goal.
- Sensitivity of displayed data and privacy/security implications.
- Environment of use: mobility, lighting, one-handed use, network quality and device class.
- Existing navigation, ViewModels, state models, Firebase/local data and permissions.
- Existing theme, typography, content density, accessibility and performance constraints.
Required workflow
- Confirm the design-test gate has passed or document why design cannot proceed.
- Identify domain, user type, primary flow, data sensitivity, environment and risks.
- Preserve existing architecture, ViewModels, repositories, Firebase behavior and navigation contracts.
- Choose a UI direction that supports the user's task, not just visual novelty.
- Route implementation details to related existing skills.
- Recommend tests, previews and accessibility checks for the redesigned flow.
Rules
- Never skip build/tests for visual redesign work.
- Design choices must name the context they serve.
- Do not change business logic, data ownership, Firebase rules or navigation semantics for aesthetics.
- Use Material 3 tokens and platform conventions unless the product context justifies a different pattern.
- Include accessibility, performance and security/privacy implications in the design plan.
- Prefer incremental design changes that can be reviewed and tested.
Related existing skills
Local skills to invoke
What ships with it
2 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 · 112 lines · 39 tokens per session scan A 9751b60095e8
context-aware-ui-design is a skill published in the GitHub repository GDvega/super-android-kotlin-firebase-skill (2 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 903 once invoked, about $0.0002 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
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.
flutter-design-system
Enforce Design Language System adherence in Flutter. Use when implementing design tokens, preventing hardcoded colors/spacing, or building a DLS.
compose-ui
Writes and reviews composables for Compose and CMP: the Route/Screen/leaf split, state-read placement and stability, loading/empty/error UX states, LazyColumn lists and grids, animation choice, accessibility and semantics, design-system tokens, CMP Res resources, Coil images, and keyboard/focus. Use when touching…
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.
compose-visuals-footguns
Compose look-and-feel traps: theme and colour tokens, artwork palettes, gradients and scrims, shimmer, glass and particle effects, animation, image loading, charts and stats displays (percent changes, shares, buckets). Use when a visual bands, pops, freezes or misleads.