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 agentmods add skills/thisissadeghi/kmpilot/using-design-systemnpx skills add ThisIsSadeghi/KMPilot --skill using-design-systemgit clone --depth 1 https://github.com/ThisIsSadeghi/KMPilotWrote 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/thisissadeghi/kmpilot/using-design-system)<a href="https://agentmods.dev/skills/thisissadeghi/kmpilot/using-design-system"><img src="https://agentmods.dev/badge/skills/thisissadeghi/kmpilot/using-design-system.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.01088 |
| Opus 5 | $0.00018 | $0.00544 |
| Sonnet 5 | $0.00007 | $0.00218 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
using-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 4d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Design System
Use X-components from :core:designsystem instead of Material3 in feature modules.
Architecture Reference: @../_shared/patterns.md
Design-Aware Mode
If a Stitch design blueprint exists (.claude/docs/{featurename}/designs/{featurename}_blueprint.md with blueprintConsumed == false in stitch-project.json.features[featurename]), implementation skills auto-detect it and use the blueprint's component tree for UI implementation. This skill provides component mappings for existing code.
Core Rule
X-components ONLY in features. NO Material3 components.
Common Replacements
| Material3 | X-component |
|---|---|
Button |
XButton (7 variants) |
TextField |
XTextField |
Text |
XText |
Scaffold (feature screen) |
XScreen (Rule 13 — XScaffold is app-shell only) |
CircularProgressIndicator |
XCircularProgressIndicator |
coil3.compose.AsyncImage |
{CORE_DESIGNSYSTEM_PKG}.AsyncImage |
Full mappings: @references/component-mappings.md Usage examples: @references/usage-examples.md
Key Rules
- Imports:
import {CORE_DESIGNSYSTEM_PKG}.*(avoid Material3 in features) - 4-State UI: Uninitialized → Loading → Success → Failed (mandatory)
- Theme: Never wrap screens in
XTheme(app-level only). Feature screens useXScreen(Rule 13) — never aScaffold/XScaffold, which would nest a second Scaffold and double the insets - Navigation: Use
XNavHost(pre-configured animations) - ScreenRoot Pattern:
{Feature}Screen+{Feature}ScreenRootpair required - Strings (Rule 12):
XText/XIcontext args takestringResource(Res.string.*), never literals. Shared strings viaDesignSystemResources; ViewModel-origin viaUiText. See@../_shared/patterns.md→ "Strings & Localization (Rule 12)". - Typography (app-global type scale): text picks an M3 type-scale role —
style = MaterialTheme.typography.{role}(or anXTextDefaultspreset) — never rawfontSize/fontWeight/fontFamily, except a blueprint-recorded override (…typography.{role}.copy(...)). The font family is global (wired inXTheme.kt), never set per-screen. See@../_shared/patterns.md→ "Typography".
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.
- 4d ago First seen · 69 lines · 37 tokens per session scan A 26938bbd9f29
using-design-system is a skill published in the GitHub repository ThisIsSadeghi/KMPilot (56 stars, last pushed 26d ago), licensed MIT. It adds 37 tokens to every session and 1,088 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-30.
Other skills, from other repositories
compose-focus-navigation
Use when writing or reviewing Jetpack Compose UI for TV, keyboard, desktop, accessibility focus, D-pad navigation, FocusRequester, focusProperties, key events, or initial focus behavior.
create-wot-ui-theme
为 wot-ui 生成单文件主题 SCSS，并在用户明确要求接入时追加 App.vue 的 @use。当用户要做品牌主题、语义变量落地、单文件主题接入时使用。.
android-accessibility
Expert checklist and prompts for auditing and fixing Android accessibility issues, especially in Jetpack Compose.
frontend-design
Designs, builds, or refactors user-facing web or application interfaces with deliberate visual direction, typography, color and spacing tokens, content hierarchy, responsive behavior, accessible interaction states, and real rendered-surface verification. Use for pages, components, dashboards, landing pages, design…
compose-multiplatform
Use when building one shared Compose UI in Kotlin across Android, iOS, and desktop — commonMain @Composables, expect/actual, source-set placement, native interop, multiplatform ViewModel/navigation/Koin. NOT a single-platform native build (that is kotlin-android / swift-ios), and NOT Dart/Flutter cross-platform UI…
design
Use for UI, UX, visual hierarchy, frontend-design judgment, references, redesigns, and design critique when the user's Emulo taste should guide the task. Do not use for unrelated execution or marketing/social writing alone.