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 thisisAhsanIqbal/nextjs-seo-audit --skill mobile-optimizationgit clone --depth 1 https://github.com/thisisAhsanIqbal/nextjs-seo-auditWrote 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/thisisahsaniqbal/nextjs-seo-audit/mobile-optimization)<a href="https://agentmods.dev/skills/thisisahsaniqbal/nextjs-seo-audit/mobile-optimization"><img src="https://agentmods.dev/badge/skills/thisisahsaniqbal/nextjs-seo-audit/mobile-optimization/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/thisisahsaniqbal/nextjs-seo-audit/mobile-optimization"><img src="https://agentmods.dev/badge/skills/thisisahsaniqbal/nextjs-seo-audit/mobile-optimization.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.00039 | $0.00628 |
| Opus 5 | $0.00019 | $0.00314 |
| Sonnet 5 | $0.00008 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
mobile-optimization 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 9d 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.
This is a copy
86% identical to oraclaw-decide — 112 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Optimization
Audit the page for mobile-friendliness.
1. Viewport meta tag
| Check | Status |
|---|---|
Missing <meta name="viewport"> |
❌ FAIL "Page will not render correctly on mobile" |
Present but missing width=device-width |
⚠️ WARN |
Contains user-scalable=no or maximum-scale=1 |
⚠️ WARN "Disabling zoom hurts accessibility" |
| Properly configured | ✅ PASS |
2. Fixed-width elements
Scan all elements with inline style="..." for width: Npx:
- If any element has
width > 500px→ ⚠️ WARN "May cause horizontal scrolling on mobile" - Report the count of offending elements
3. Font sizes
Scan inline styles for font-size: Npx:
- If any element has
font-size < 12px→ ⚠️ WARN "Difficult to read on mobile" - Report the count
4. Touch target sizes
Check interactive elements (<a>, <button>, <input type="submit">, <input type="button">) with inline height style:
- If
height < 48px→ ⚠️ WARN "Too small for touch targets" - Minimum recommended: 48px × 48px (per Google's mobile-friendly guidelines)
5. Overflow detection
- Elements with
overflow-x: hiddenoroverflow: hidden→ ⚠️ WARN "Verify content is not clipped on mobile"
6. Responsive stylesheets
<link rel="stylesheet" media="...">found → ✅ PASS "Media-query-specific stylesheets found"
7. Tables
- If > 2
<table>elements → ⚠️ WARN "Tables can be difficult to read on mobile. Consider responsive table patterns"
Edge cases
- If no inline styles are present, skip fixed-width and font-size checks
- CSS-in-JS frameworks (styled-components, Emotion) embed styles at runtime — these cannot be audited from static HTML alone; note this limitation
- Elements with
display: noneorvisibility: hiddenshould be excluded from touch target checks - AMP pages have their own viewport rules — flag but do not fail if AMP boilerplate is detected
- PWA splash screens and app-shell patterns may intentionally use
user-scalable=no— flag as ⚠️ WARN but note context
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.
- 9d ago First seen · 67 lines · 39 tokens per session scan A 8c477ca138fb
mobile-optimization is a skill published in the GitHub repository thisisAhsanIqbal/nextjs-seo-audit (7 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 628 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to oraclaw-decide, differing in 112 lines, and is treated as a copy.
Other skills, from other repositories
swiftui-app-architecture-workflow
Guide SwiftUI app-structure decisions for Apple apps across App, scenes, commands, focus, environment, preferences, window and document coordination, and reusable view composition. Use when the user wants help deciding where ownership belongs in a SwiftUI app, which data-flow mechanism fits a responsibility, or how to…
maui-shell-navigation
Guide for implementing Shell-based navigation in .NET MAUI apps. Covers AppShell setup, visual hierarchy (FlyoutItem, TabBar, Tab, ShellContent), URI-based navigation with GoToAsync, route registration, query parameters, back navigation, flyout and tab configuration, navigation events, and navigation guards. Use when…
react-native-architecture
Production-ready patterns for React Native development with Expo, including navigation, state management, native modules, and offline-first architecture.
react-native-expert
React Native development expertise. Navigation, native modules, performance, animations, and cross-platform patterns. Use when building mobile apps with React Native or Expo.
building-native-ui
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
rn-data-fetching
Expert guidance on TanStack Query v5 in React Native -- queries, mutations, optimistic updates, polling, retries, and offline behavior. Use when asked about data fetching, caching, or server state.