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 Kemdirimakujuobi/skills --skill mobile-responsive-reviewgit clone --depth 1 https://github.com/Kemdirimakujuobi/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/kemdirimakujuobi/skills/mobile-responsive-review)<a href="https://agentmods.dev/skills/kemdirimakujuobi/skills/mobile-responsive-review"><img src="https://agentmods.dev/badge/skills/kemdirimakujuobi/skills/mobile-responsive-review/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/kemdirimakujuobi/skills/mobile-responsive-review"><img src="https://agentmods.dev/badge/skills/kemdirimakujuobi/skills/mobile-responsive-review.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.00153 | $0.02852 |
| Opus 5.5 | $0.00061 | $0.01141 |
| Sonnet 5.5 | $0.00031 | $0.00570 |
| Haiku 4.5 | $0.00015 | $0.00285 |
Grade A, and why
mobile-responsive-review 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 13d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile responsive review
Making an existing app usable on phones is usually one big pass of max-md: class additions across
hundreds of files. Every new page that ships desktop-only undoes a little of that pass. This skill is
the check that keeps a new surface from regressing it, and it carries the traps that pass hit so you
don't rediscover them in review.
This is a blocker. A UI diff that breaks at phone width does not get pushed. The opt-out is explicit, not silent: put one line in the PR body —
Mobile impact: none — <reason>(no visible layout change), orMobile: desktop-only — <reason>(a surface that genuinely can't work on a phone, e.g. a drag-and-drop canvas editor) — and the gate is green.
Configure for your repo
- Tailwind, with the default
mdbreakpoint (48rem, 768px). The scanner and fixes assumemax-md:/max-sm:variants exist (Tailwind v3.2+; the traps below are written for v4). - Base branch — read from
AGENTS.md; defaultorigin/main. Pass it to the scanner with--base <ref>orMOBILE_SCAN_BASE. - UI roots — default
app,components,src. Override with--dirs a,borMOBILE_SCAN_DIRS. - Exempt surfaces — dev/preview/test routes that never ship. List them in
AGENTS.mdand pass each as--skip '<regex>'(or comma-separated inMOBILE_SCAN_SKIP). Tests and stories are always skipped. - What your app shell already does on phones (drawer nav, gutters, phone-safe table and dialog
primitives) — note it in
AGENTS.mdso reviewers don't redo it. See "Know what's already handled". docs/standards/STANDARDS.md— COMP-01 (accessible primitives) and HYG-02 (visible change evidence) are referenced below; stated in words if the file is missing.
The contract
- Phone = below Tailwind's
mdbreakpoint (48rem, 768px). Target 360–430px wide. - Desktop must not change. At >= 768px every computed style stays exactly as it was. So fix phone
layouts by adding
max-md:/max-sm:classes, not by rewriting base classes. A base-class change is only acceptable if it renders identically at >= 768px (e.g.grid-cols-1 md:grid-cols-3replacinggrid-cols-3). - This is a code-reading check. No browser needed; the reviewer confirms in devtools device mode (Step 6).
What ships with it
1 file 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.
- 13d ago First seen · 168 lines · 153 tokens per session scan A 715a092b00dd
mobile-responsive-review is a skill published in the GitHub repository Kemdirimakujuobi/skills (9 stars, last pushed 13d ago), licensed MIT. It adds 153 tokens to every session and 2,852 once invoked, about $0.0006 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-10-15.
Other skills, from other repositories
design-engineering
Premium design engineering skill for agentic workflows — produces high-end, distinctive UI designs using DESIGN.md as the portable contract across Pencil MCP (in-IDE canvas), Figma MCP (team handoff + design tokens), and Google Stitch (vibe exploration + AI generation). Enforces anti-generic principles, WCAG 2.2 AA…
memoire-design-tooling
Set up and operate Mémoire's CLI, MCP server, agent kits, design preflight, UX audits, craft checks, tokens, and registry evidence. Use when a repository explicitly needs Mémoire tooling; use portable design skills when Mémoire is unavailable.
better-typography
Web typography from choosing fonts to spacing, wrapping and accessibility. Use when picking or pairing typefaces, configuring variable fonts or OpenType features, setting up a type scale, checking heading hierarchy, styling text in components, truncating text, styling underlines, selection, placeholders or carets, or…
better-ui
Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better"…
token-architecture
Map design values to an existing token system and plan safe token changes across themes and consumers. Use for token drift, Figma variable alignment, or cross-surface theming.
design-to-code-handoff
Carry Figma or Paper design evidence into an existing web codebase, design system, Storybook, and browser verification. Use when an agent must implement a supplied design without losing source context or inventing components.