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/plugin87/full-stack-design-skills/responsive-universal-designnpx skills add plugin87/full-stack-design-skills --skill responsive-universal-designgit clone --depth 1 https://github.com/plugin87/full-stack-design-skillsWhat 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.00123 | $0.04129 |
| Opus 5 | $0.00062 | $0.02065 |
| Sonnet 5 | $0.00025 | $0.00826 |
| Haiku 4.5 | $0.00012 | $0.00413 |
Grade A, and why
responsive-universal-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 2d 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 — 699 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Responsive & Universal Design
Principles and practices for designing products that work beautifully across all devices and screen sizes.
Responsive design isn't just about making things smaller on mobile—it's about rethinking the entire experience for different contexts. Mobile-first design means starting with the most constrained device (mobile) and progressively enhancing for larger screens.
Core Principle: Mobile-First Design
Why Mobile-First?
Mobile users face real constraints:
- Small screen (360-480px) — less visual real estate
- Touch interaction — larger touch targets needed (48px minimum)
- Limited bandwidth — fewer/smaller images
- One-handed use — thumb-reachable zones matter
- On-the-go context — simpler, more focused tasks
Designing for mobile first forces you to prioritize ruthlessly. You can't fit everything on a 375px screen, so you cut the noise. Then, for larger screens, you add back layers of complexity.
Principle: Start with mobile, progressively enhance for larger screens (not the reverse).
Mobile-First Workflow
Traditional approach (desktop-first):
1. Design at 1440px (desktop)
2. Squish into 375px (mobile)
3. Things break, cut features
4. Result: Poor mobile experience
Mobile-first approach:
1. Design at 375px (mobile)
2. Expand to 768px (tablet)
3. Expand to 1440px (desktop)
4. Result: Intentional, layered experience
Responsive Breakpoints
Standard Device Breakpoints
Define breakpoints based on design needs, not device sizes. But here's a practical starting point:
Mobile (small): 320px - 479px (phones in portrait)
Mobile (large): 480px - 639px (larger phones, landscape)
Tablet: 640px - 1023px (tablets in portrait)
Desktop: 1024px - 1439px (laptops, small desktops)
Desktop (large): 1440px + (large desktops, 4K)
Implementation in CSS
/* Mobile-first: Base styles for mobile */
.container {
width: 100%;
padding: 16px;
display: flex;
flex-direction: column; /* Stack vertically on mobile */
}
/* Tablet: 640px and up */
@media (min-width: 640px) {
.container {
width: 90%;
margin: 0 auto;
flex-direction: row; /* Side-by-side on tablet */
}
}
/* Desktop: 1024px and up */
@media (min-width: 1024px) {
.container {
width: 1200px;
max-width: 100%;
}
}
What ships with it
4 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.
- 2d ago First seen · 699 lines · 0 tokens per session scan A a7571aa4e9e8
responsive-universal-design is a skill published in the GitHub repository plugin87/full-stack-design-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 123 tokens to every session and 4,129 once invoked, about $0.0006 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
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
react-native-ease-refactor
Scan for Animated/Reanimated code and migrate to EaseView.
moq
Build live video, audio, and real-time data apps with Media over QUIC (MoQ). Use when adding live streaming, conferencing, voice AI, or real-time pub/sub to an app; when integrating the @moq/ npm packages, moq- Rust crates, or the Python/Kotlin/Swift/Go/C bindings; or when running a moq-relay server or a gateway…