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/hyperlogue/r3/mobile-tiernpx skills add hyperlogue/r3 --skill mobile-tiergit clone --depth 1 https://github.com/hyperlogue/r3Wrote 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/hyperlogue/r3/mobile-tier)<a href="https://agentmods.dev/skills/hyperlogue/r3/mobile-tier"><img src="https://agentmods.dev/badge/skills/hyperlogue/r3/mobile-tier.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.1 | $0.00000 | $0.01533 |
| Opus 5 | $0.00000 | $0.00766 |
| Sonnet 5 | $0.00000 | $0.00307 |
| Haiku 4.5 | $0.00000 | $0.00153 |
Grade A, and why
mobile-tier 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The phone tier
This file is the design source of truth for r3 below Tailwind md — update it
here when the mobile design changes.
Phones are not first-class: no productive authoring is expected. But reading
code, switching rounds/snapshots, reading feedback, resolve/submit, replying, and
adding feedback all work below md (768px). Portrait tablets keep the desktop
layout.
The prime rule: isolate, don't interleave
Mobile must not add complexity to desktop code.
- All mobile UI lives in
web/src/mobile/, and desktop components never import from it. - Existing components get only inert
max-md:/pointer-coarse:class tweaks. The one exception isJumpToFile's inlinematchMedia("(pointer: coarse)")probe, which suppresses autofocus on touch — it can't importusePointerCoarsewithout breaking the isolation rule. - The single mount point is
ReviewView, which swaps the side dock forMobileReviewChrome. Panel and domain state never fork, and the sameFeedbackPanelrenders with the same props either way.
web/src/mobile/ holds containers only: useIsMobile + usePointerCoarse
(both over useMediaQuery), MobileReviewChrome (bottom bar + the 3-state
feedback sheet), and AddFeedbackPill (the touch selection-anchor pill).
Side-by-side diffs never render below md. Two code columns don't fit a phone
pane, so ReviewView forces layout="unified" and PaneToolbar hides the toggle
(max-md:hidden, an inert class — desktop components still don't import from
mobile/). The override deliberately does not write the persisted preference,
so a split-preferring reader gets split back on a wide viewport.
Layout
The sidebar hides. The pane toolbar wraps into stacked full-width rows — round/snapshot selector (full-bleed trigger, chevron far right) · the round summary · the buttons.
The whole header stack (review header, review summary, toolbar rows) mounts
inside the scroll pane on mobile. The review header + summary scroll away with
the code, while the toolbar sticks at the pane top and each file header pins
just below it. The toolbar's live height rides on the pane as --pane-sticky-h,
which FileCard's header top and the anchor-in-view test both read (unset = 0 on
desktop). So the sticky stack is toolbar + file header, the code gets the full
height between the navbar and the bottom bar, and the pane stays the one scroll
container.
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 · 126 lines · 0 tokens per session scan A 9fee77dc842a
mobile-tier is a skill published in the GitHub repository hyperlogue/r3 (25 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,533 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-08-30.
Other skills, from other repositories
app-store-optimization
Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store.
react-native-skills
React Native and Expo best practices for building performant mobile apps. Contains 35+ rules across 14 categories covering list performance, animations, navigation, UI patterns, and platform-specific optimizations. Use when building React Native components, optimizing lists, implementing animations, or working with…
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
self-assessment
Interactive skill assessment with personalized learning path generation.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.