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/codebygarv/ai-skills/responsive-checkernpx skills add codebygarv/Ai-skills --skill responsive-checkergit clone --depth 1 https://github.com/codebygarv/Ai-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/codebygarv/ai-skills/responsive-checker)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/responsive-checker"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/responsive-checker.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.00041 | $0.00517 |
| Opus 5 | $0.00020 | $0.00259 |
| Sonnet 5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
responsive-checker 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 yesterday.
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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Determine whether a UI implementation will actually hold up across mobile, tablet, and desktop viewports — not just at whatever single width it was built and eyeballed at.
When to Use
- Reviewing layout code (CSS/Tailwind/styled-components/etc.) meant to be responsive.
- Before shipping any UI intended to be used on multiple device classes.
- Debugging a specific "looks broken on mobile/tablet" report.
What to Analyze
- Breakpoint coverage — are there defined behaviors at common breakpoints (mobile ~375–428px, tablet ~768–1024px, desktop 1280px+), or does the layout only really work at one width?
- Fixed vs. fluid sizing — hardcoded pixel widths/heights that won't adapt, versus relative units (%,
fr,rem,vw/vhused appropriately) that do. - Overflow handling — content that will overflow, get clipped, or force horizontal scroll at narrow widths (long text, wide tables, fixed-width images).
- Touch target sizing — interactive elements meeting a reasonable minimum touch target size (~44x44px) on mobile, not just sized for mouse precision.
- Layout reflow — does a multi-column desktop layout collapse sensibly on mobile (stacking, hiding secondary content, or reflowing), or does it just shrink until unreadable?
- Text scaling — font sizes and line lengths that stay readable at mobile widths, not desktop-sized text crammed into a narrow viewport.
Output Format
- Findings organized by viewport class (Mobile / Tablet / Desktop) where the issue manifests, or "All viewports" if it's breakpoint-independent.
- Each finding: what breaks, at roughly what width, and the fix (a specific CSS/layout change).
- If reviewing code without a live render, note explicitly which findings are code-inferred vs. would benefit from an actual visual check at that width.
Avoid
- Assuming a specific breakpoint strategy the codebase doesn't use — check existing breakpoint conventions first and match them.
- Flagging a deliberately mobile-hidden or desktop-only element as broken when it's an intentional responsive choice.
- Recommending a full layout rewrite when a targeted breakpoint fix solves the actual issue.
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.
- yesterday First seen · 36 lines · 41 tokens per session scan A 49c5b077368f
responsive-checker is a skill published in the GitHub repository codebygarv/Ai-skills (25 stars, last pushed 16d ago), licensed MIT. It adds 41 tokens to every session and 517 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-09-03.
Other skills, from other repositories
bun-api
Bun runtime API reference for TypeScript scripts. Covers Bun.serve() HTTP/HTTP/2 server with routes and WebSockets, fetch() transport options, Bun.file(), Bun.write(), Bun.$() shell, Bun.spawn(), Bun.Glob, Bun.env, bun:sqlite, Bun.sql() for PostgreSQL/MySQL via DATABASEURL, Bun.s3 for S3-compatible storage, Bun.redis…
bun-cli
Bun CLI reference for package management, script running, testing, bundling, and compilation. Covers bun install/add/remove/update, bun run, bun test, bun build, bunx, bun patch, bun audit fix, bun dedupe, bun prune, bun why, bun pm, bun repl, bunfig.toml, bun.lock, workspace catalogs, isolated installs and the global…
deps-upgrade
Validate JavaScript/TypeScript dependency upgrades after an interactive or manual update. Establish the real delta from git, detect peer/engine/type conflicts, extract breaking changes, migrations and adoptable features from release notes, assess held-back or seemingly unused packages, and run verification gates.…
git-pr
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing…
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
git-ci
CI/CD status queries for GitHub Actions (gh) and GitLab CI (glab). Check pipeline status, failing jobs, workflow runs, job logs, and merge readiness. Use when checking CI status, debugging build failures, viewing job logs, watching pipeline progress, or configuring gh/glab CI read-only allowlists. Not for PR workflows…