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 dembrandt/dembrandt-skills --skill responsive-paradigmsgit clone --depth 1 https://github.com/dembrandt/dembrandt-skillsWrote 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/dembrandt/dembrandt-skills/responsive-paradigms)<a href="https://agentmods.dev/skills/dembrandt/dembrandt-skills/responsive-paradigms"><img src="https://agentmods.dev/badge/skills/dembrandt/dembrandt-skills/responsive-paradigms/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/dembrandt/dembrandt-skills/responsive-paradigms"><img src="https://agentmods.dev/badge/skills/dembrandt/dembrandt-skills/responsive-paradigms.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00033 | $0.02188 |
| Opus 5.5 | $0.00013 | $0.00875 |
| Sonnet 5.5 | $0.00007 | $0.00438 |
| Haiku 4.5 | $0.00003 | $0.00219 |
Grade A, and why
responsive-paradigms 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 18d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Responsive Paradigms
Mobile, tablet, and desktop are fundamentally different interaction contexts. The input method, screen real estate, viewing distance, and session intent all differ. Responsive design is not the same layout at different widths — it is a different design decision at each breakpoint.
The Three Paradigms
Mobile (< 768px)
- Input: Touch — fingers, not a cursor. Tap targets ≥ 44×44px.
- Navigation: Bottom tab bar (thumb reachable) or hamburger drawer. Top navigation is hard to reach.
- Session: Often interrupted, task-focused, shorter. Show the most important thing first.
- Content: Single column. Vertical scroll only. No hover states.
- Primary action: Floating action button (FAB) or full-width button at the bottom of the screen.
Tablet (768px–1024px)
- Input: Touch and sometimes keyboard/trackpad. Hybrid paradigm.
- Navigation: Can support a persistent sidebar at landscape orientation; collapses to drawer at portrait.
- Content: Two-column layouts work. Master-detail patterns (list + detail side by side) are natural.
- Primary action: Can be in-line with content, not necessarily floating.
Desktop (> 1024px)
- Input: Mouse with hover states, keyboard shortcuts, precise clicking.
- Navigation: Persistent sidebar or top navigation. Both visible simultaneously.
- Content: Multi-column, dense information, toolbars, context menus.
- Primary action: In-context with content, supported by keyboard shortcuts for power users.
Section Behaviour Across Breakpoints
Not every section needs to appear on every breakpoint at the same position — or at all.
Sections can be hidden on mobile
Secondary content (related articles, supplementary sidebars, decorative illustrations) can be hidden below a breakpoint. Ask: does a mobile user need this? If no, display: none at mobile is correct.
Stacking is the default; repositioning is allowed within the same container
The default responsive move is simply to stack — a horizontal row of blocks becomes a vertical column as the viewport narrows. This preserves order and grouping, so the user's mental model of the page survives the breakpoint unchanged. Reach for it first.
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.
- 18d ago Changed · +5 lines ecd57f6d852f
- 25d ago Changed · -35 tokens per session ede933b611d4
- 1mo ago First seen · 193 lines · 68 tokens per session scan A 0cf4c9a8bb65
responsive-paradigms is a skill published in the GitHub repository dembrandt/dembrandt-skills (169 stars, last pushed 5d ago), licensed MIT. It adds 33 tokens to every session and 2,188 once invoked, about $0.0001 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-30.
Other skills, from other repositories
indian-gov-web-ui
A set of design and accessibility rules for Indian government websites, portals, and administrative panels, including required standards such as GIGW and WCAG.
ux4g-design-system
Use when building or reviewing UI with UX4G — India's official government design system (ux4g.gov.in, cdn.ux4g.gov.in, ux4g-web-components). Covers the v3.0.18 token API, the 52 components, install paths for HTML/React/Angular/Flutter, and the interop hazards. Triggers include "UX4G", "ux4g-web-components"…
design-doctrine
The house rules for ANY design or UI work - the verification protocol (run the gate, never claim a number), the absolute no-emoji rule, token by intent, one shared theme, the eight states, one thing leads, and output completeness. Load this FIRST whenever building, reviewing, or theming a screen, component, or token…
image-to-code
Turn a reference image, screenshot, or mockup into token-driven, accessible code. Infer the design system from the reference (palette, type scale, spacing, radius, layout archetype), map it to the 3-tier tokens, rebuild it, then verify with the kit's gates. Use when the user provides a design/screenshot and wants…
design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides…
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.