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 compose-contextual-design-systemgit 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/compose-contextual-design-system)<a href="https://agentmods.dev/skills/gdvega/super-android-kotlin-firebase-skill/compose-contextual-design-system"><img src="https://agentmods.dev/badge/skills/gdvega/super-android-kotlin-firebase-skill/compose-contextual-design-system/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/compose-contextual-design-system"><img src="https://agentmods.dev/badge/skills/gdvega/super-android-kotlin-firebase-skill/compose-contextual-design-system.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.00038 | $0.00814 |
| Opus 5 | $0.00019 | $0.00407 |
| Sonnet 5 | $0.00008 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
compose-contextual-design-system 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 9d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Shape a Compose design system around the product context, while preserving architecture and testability.
When to use
- Creating or refactoring reusable Compose components.
- Defining Material 3 color, typography, spacing, shape, elevation or motion decisions.
- Turning repeated screen UI into a small component system.
- Reviewing whether AI-generated components are reusable, accessible and consistent.
Inputs to inspect
- Gate result from
design-test-gate. - Existing theme files and Material 3 setup.
- Reusable components, previews and component tests.
- Product context from
context-aware-ui-design. - Edge-to-edge/adaptive requirements.
- Performance-sensitive components such as lists, cards, images and animations.
Required workflow
- Confirm build/tests passed before changing theme or components.
- Identify existing tokens and component ownership.
- Decide which components are product-specific and which should stay local to a screen.
- Define component contracts: state, slots, callbacks, semantics and preview states.
- Preserve stable APIs and avoid broad visual rewrites.
- Add or recommend previews/tests for component states and accessibility.
Rules
- Use existing Material 3 theme tokens before adding new ones.
- Do not create a design system for one-off UI.
- Keep reusable components stateless where possible.
- Do not pass ViewModels into reusable design components.
- Avoid experimental APIs unless the user explicitly accepts the risk.
- Check performance risks for reusable list items and animated components.
Related existing skills
Local skills to invoke
- jetpack-compose
- xml-to-compose-migration
- edge-to-edge-adaptive-ui
- compose-performance
- accessibility
External companion skills to use when installed
Do not assume these companion skills are installed. Prefer the local skills above first, then consult Companion Skills for install and verification commands.
- aldefy/compose-skill — use for deeper Jetpack Compose, Material 3, design-to-code, theming or Compose architecture guidance.
- skydoves/compose-performance-skills — use for deeper Compose performance, recomposition, stability or release-mode measurement guidance.
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.
- 9d ago First seen · 110 lines · 38 tokens per session scan A 9b1f1de22be6
compose-contextual-design-system is a skill published in the GitHub repository GDvega/super-android-kotlin-firebase-skill (2 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 814 once invoked, about $0.0002 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
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.
android-jetpack-compose-expert-v2
Android Jetpack Compose Expert workflow skill. Use this skill when the user needs Expert guidance for building modern Android UIs with Jetpack Compose, covering state management, navigation, performance, and Material Design 3 and the operator should preserve the upstream workflow, copied support files, and provenance…
m3-expressive
Material 3 Expressive design patterns for Jetpack Compose - expressive theming, motion physics, shape morphing, typography emphasis, color emphasis, and all 28 expressive components.
liquid-glass
Apple Liquid Glass design patterns for SwiftUI iOS 26 - glass effects, morphing, containers, interactive glass, tinting, accessibility, and cross-platform glass design.