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/coinyak/onchainai/responsive-designnpx skills add Coinyak/onchainai --skill responsive-designgit clone --depth 1 https://github.com/Coinyak/onchainaiWrote 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/coinyak/onchainai/responsive-design)<a href="https://agentmods.dev/skills/coinyak/onchainai/responsive-design"><img src="https://agentmods.dev/badge/skills/coinyak/onchainai/responsive-design.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.00106 | $0.02532 |
| Opus 5 | $0.00053 | $0.01266 |
| Sonnet 5 | $0.00021 | $0.00506 |
| Haiku 4.5 | $0.00011 | $0.00253 |
Grade A, and why
responsive-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 5d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Responsive Design
Use this skill when the job is to name the failing responsive surface, choose the smallest viable adaptation packet, and leave behind a short strategy + verification brief.
The job is not to dump generic CSS recipes, paste framework snippets, or absorb every neighboring frontend concern.
This skill should:
- classify the responsive failure first,
- choose one primary responsive packet,
- keep viewport vs container ownership explicit,
- separate dense-data and media cases from generic layout advice,
- keep reflow/verification visible,
- route neighboring frontend work honestly.
Read these support docs first:
- references/intake-packets-and-route-outs.md
- references/layout-decision-checklist.md
- references/handoff-boundaries.md
When to use this skill
- A team says “this page breaks on mobile” and the real responsive surface is still unclear.
- A dashboard, nav, form, card grid, pricing page, table, or embed needs a responsive strategy before more breakpoints are added.
- You need to decide whether the fix belongs in viewport layout rules, container queries, intrinsic layout, responsive media handling, or verification/reflow follow-up.
- A launch-readiness pass uncovered overflow, wrapping, density, or zoom/reflow failures and someone needs one bounded packet instead of a CSS lecture.
- The request mixes page-level adaptation, component reuse, and dense-data pressure and needs routing before implementation.
When not to use this skill
- The main task is reusable primitive / slot / variant API design or component-family ownership →
ui-component-patterns - The main task is keyboard/focus behavior, semantics, labels, contrast, reduced motion, or accessibility-heavy remediation →
web-accessibility - The main task is breakpoint governance, token policy, or cross-product responsive standards →
design-system - The main task is broad UI critique, polish, heuristic review, or launch-readiness audit across many dimensions →
web-design-guidelines - The main task is React hydration, rerender churn, or client-boundary performance behavior →
react-best-practices - The responsive strategy is already clear and the job is just implementation; in that case implement directly instead of re-running the router
What ships with it
5 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.
- 5d ago First seen · 240 lines · 106 tokens per session scan A 14044f8eee92
responsive-design is a skill published in the GitHub repository Coinyak/onchainai (1 stars, last pushed 1mo ago), licensed MIT. It adds 106 tokens to every session and 2,532 once invoked, about $0.0005 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
kiranism-shadcn-dashboard
Guide for building features, pages, tables, forms, themes, and navigation in this Next.js 16 shadcn dashboard template. Use this skill whenever the user wants to add a new page, create a feature module, build a data table, add a form, configure navigation items, add a theme, set up RBAC access control, or work with…
sandbox
Visual HTML canvas sandbox for agent-driven UI and live previews.
omd:feel
디자인·프론트 업계가 '감'으로 쓰던 인터페이스 디테일을 수치화한 규칙으로 적용(APPLY)하거나 감사(AUDIT)한다. Jakub Krehel의 make-interfaces-feel-better 철학을 계승 + HIG/Material/WCAG/DS 토큰/실무자 리서치로 확장한 17축·113규칙(provenance 등급별). 모션 타이밍·이징·동심원 radius·tabular-nums·44px 타깃·focus ring·prefers-reduced-motion 등. 'feel 좋게 다듬어줘', '인터페이스 디테일 적용', 'feel 점검', '마이크로 인터랙션…
omd:aphrodite
Maximum-craft one-page landing — the wow bar. omd:landing 의 구조 위에 마감(서체 조달·그레인·깊이·색보정·스크롤 타임라인)과 최고급 에셋을 얹고, 랜딩 검사 전 항목 통과를 합격선으로 삼는다. Trigger: '와우', '압도적인', '최고급', '쇼케이스용', 'aphrodite', '데모용 랜딩', '이거 자랑할 거야'.
omd:landing
Scroll-native one-page landing that overwhelms — concept, composition, asset placement, and scroll choreography derived from DESIGN.md and the measured landing-craft codex. Trigger: '랜딩 페이지', '원페이지', 'landing page', 'one-pager', 'hero to footer', '스크롤 랜딩', 'affinity.studio 같은'.
omd:showcase
Turn a rendered page (or several, side by side) into a scroll demo video — deterministic frame capture, ffmpeg H.264/GIF, labels per arm. Trigger: '시연 영상', '스크롤 영상 만들어', 'showcase', 'demo video', '비교 영상', 'record the page'.