mobile-resume

mobile-resume is a skill for Claude Code from suntay44/web-to-mobile-magic-plugin. It costs 34 tokens per session (405 once invoked), scanned A, original, MIT.

A workflow for inspecting and finishing an incomplete Expo React Native or Swift mobile app. It checks the app, creates a completion plan, and follows different steps depending on the mobile technology.

In plain words
What is it for?
Use it to audit a mobile app, create a dated checklist and test plan, finish approved missing features in Expo or React Native apps, and verify the result before release.
Why use it?
It shows what is finished, partly done, or missing before more code is written. This helps prevent rebuilding completed work and requires approval before implementation.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the web-to-mobile plugin — 11 skills, 6 commands shipped together

Good fit Use it to audit a mobile app, create a dated checklist and test plan, finish approved missing features in Expo or React Native apps, and verify the result before release.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/suntay44/web-to-mobile-magic-plugin/mobile-resume
Install

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.

Any agent
npx skills add suntay44/web-to-mobile-magic-plugin --skill mobile-resume
Clone the repo
git clone --depth 1 https://github.com/suntay44/web-to-mobile-magic-plugin

Made for: Claude Code.

Or install web-to-mobile, the plugin that ships this one along with the rest of its 11 skills, 6 commands.

Wrote 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.

agentmods badge for mobile-resume

README.md
[![agentmods](https://agentmods.dev/badge/skills/suntay44/web-to-mobile-magic-plugin/mobile-resume/github.svg)](https://agentmods.dev/skills/suntay44/web-to-mobile-magic-plugin/mobile-resume)
Your own site
<a href="https://agentmods.dev/skills/suntay44/web-to-mobile-magic-plugin/mobile-resume"><img src="https://agentmods.dev/badge/skills/suntay44/web-to-mobile-magic-plugin/mobile-resume/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.

agentmods 80×15 button for mobile-resume

Your own site · 80×15
<a href="https://agentmods.dev/skills/suntay44/web-to-mobile-magic-plugin/mobile-resume"><img src="https://agentmods.dev/badge/skills/suntay44/web-to-mobile-magic-plugin/mobile-resume.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 405 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high System Prompt Leakage · line 46
    Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
    Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.00405
Opus 5 $0.00017 $0.00202
Sonnet 5 $0.00007 $0.00081
Haiku 4.5 $0.00003 $0.00040

Measured yesterday against content hash 5b162ad49905, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

mobile-resume 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.

skills/mobile-resume/SKILL.md · 45 lines

What it actually says

MobileResume

Invoke /mobile-resume [local_path | github_repo_url] or ask to use this skill.

Route The Workflow

First look for a plan matching the target and requested work under docs/mobile-resume/ or docs/web-to-mobile/. Check Source, status/approval, unchecked items, and relevant changes since its recorded evidence; do not choose by date alone. For a usable plan, refresh only stale findings, preserve completed items, and continue its next phase. Missing approval returns to planning; changed scope needs approval. If matching or freshness cannot be established, audit first. Never infer approval from checkboxes.

Otherwise use one phase skill at a time:

  1. mobile-app-audit records completion status and evidence.
  2. mobile-completion-plan writes docs/mobile-resume/YYYY-MM-DD-mobile-completion-plan.md.
  3. After approval, expo-react-native-build implements unchecked items for Expo/React Native. Hand Swift plans to the existing native workflow; never invoke the Expo builder.
  4. mobile-qa-release verifies implementation before completion.

Do not generate or edit app code until a plan exists and the user approved it.

Target Classification

  • No argument: use the current workspace as the mobile app source.
  • https://github.com/<owner>/<repo>: clone or inspect the repo if permitted; otherwise ask for a local checkout.
  • Local path: inspect files directly.

Stack

Continue in the audited stack unless the user explicitly requests a switch.

Output Rules

  • Use the Markdown plan as external memory and the source of truth.
  • Re-read only the relevant plan sections for each phase.
  • Reference actual files, screens, navigators, dependencies, and commands.
Changes

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.

  1. yesterday Changed · -6 lines · -13 tokens per session 5b162ad49905
  2. 10d ago First seen · 51 lines · 47 tokens per session scan A 0243016c0c9a

Subscribe to this mod's changes

mobile-resume is a skill published in the GitHub repository suntay44/web-to-mobile-magic-plugin (106 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 405 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-08-30.

Related

Other skills, from other repositories

orca-emulator-android

Android device and emulator control from inside Orca over adb, with the live device view in Orca's emulator pane. Use when driving an adb-connected emulator or phone on Windows, Linux, or macOS: booting AVDs, taps, swipes, typing, hardware buttons, rotation, app install and launch, runtime permissions, the…

stablyai/orca · 102 tokens

android-tombstone-symbolication

Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…

dotnet/skills · 176 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

winapp-maui

Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.

microsoft/winappCli · 71 tokens

react-native-ease-refactor

Scan for Animated/Reanimated code and migrate to EaseView.

appandflow/react-native-ease · 18 tokens

apple-search-ads

When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…

Eronred/aso-skills · 127 tokens