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 commands/eddiebelaval/squire/mobile-checkgit clone --depth 1 https://github.com/eddiebelaval/squireWrote 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/commands/eddiebelaval/squire/mobile-check)<a href="https://agentmods.dev/commands/eddiebelaval/squire/mobile-check"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/mobile-check.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.00000 | $0.00397 |
| Opus 5 | $0.00000 | $0.00198 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
mobile-check 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.
What it actually says
Mobile Readiness Check
You are invoking the mobile-check skill - comprehensive mobile viewport verification using Playwright MCP.
Load and follow the skill at: .claude/skills/mobile-check/SKILL.md
Mode Selection
Parse $ARGUMENTS to determine mode:
- Empty → Full mobile audit of all detected pages (cap at 10)
- URL/route → Check that specific page (e.g., "/dashboard", "/login")
- Multiple routes → Check each listed route
- "extreme" → Also test at 320px (iPhone SE 1st gen) after 375px pass
- "tablet" → Also check at 768px (iPad Mini)
Quick Reference
Setup
1. Detect dev server (localhost:3000, 3001, 8080)
2. If not running, start it
3. browser_resize({ width: 375, height: 667 })
Per-Page Audit Sequence
1. browser_navigate to page
2. browser_snapshot for accessibility tree
3. browser_evaluate — run horizontal overflow check
4. browser_evaluate — run touch target check
5. browser_evaluate — run text size check
6. browser_evaluate — run viewport meta check
7. browser_evaluate — run fixed/sticky element check
8. browser_evaluate — run input type check (if forms present)
9. browser_console_messages — check for errors
10. browser_network_requests — check for failures
11. browser_take_screenshot — save visual proof
Key Thresholds
- Viewport: 375x667 (iPhone mini/SE) — the floor
- Touch targets: minimum 44x44px (Apple HIG)
- Text: minimum 12px rendered
- Inputs: minimum 44px height, proper type attributes
Arguments
$ARGUMENTS
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 · 48 lines · 0 tokens per session scan A 30b185dcb091
mobile-check is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 397 tokens. 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 commands, from other repositories
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
paul:verify
Guide manual user acceptance testing of recently built features.
cover
Generate tests that do not exist yet. Analyzes coverage gaps, then writes and runs new test files across three tiers (unit, integration via testcontainers, Playwright E2E), one test-generator agent per tier, healing failures for up to 3 iterations. Use when code has no tests or when raising coverage after…
spec-check
Audit GWT acceptance test specs for implementation leakage. Optionally provide a specific file path.
drift
Detectar divergencias entre specs Gherkin e implementación (spec drift). Usa cuando el usuario dice "spec drift", "drift detection", "spec vs código", "conformance check", "spec deviation", "código no matchea specs", "implementation diverged", "spec vs implementation", "verificar specs". Compara features implementadas…