Skip to main content
prompt GP ChatGPT

phone_sms_login — Claude Code prompt: what it does, how to install

phone_sms_login — a prompt for Claude Code and ChatGPT logs into an Android app via SMS on explicit user request. Device credentials stay local and never reach the model.

Apache-2.0 ★ 9,488 updated 2026-11-16

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/phone_sms_login.md
Open on GitHub

What phone_sms_login does

The prompt guides the assistant to complete SMS-based authentication for a specified Android package. The host machine selects a trusted local profile containing account details and interface mappings, captures the matching incoming SMS, inserts the verification code, and taps the sign-in button. It confirms login status strictly on-device using local OCR checks on the landing screen.

The prompt strictly forbids reading codes via chat, screenshots, sandbox tools, notifications, or MCP servers. CAPTCHA challenges, payment steps, account recovery, registration flows, and WebViews fall outside its scope, triggering an immediate handoff to manual user control.

What it helps with

  • complete SMS login flows inside Android applications
  • verify sign-in status on-device with local OCR
  • keep sensitive one-time codes and credentials outside model context
  • hand over control to the user when facing CAPTCHAs or risk checks

Example prompts for the agent

  • Log into the Android app with package com.example.app via SMS
  • Sign in to com.service.client using my saved device profile

How to install phone_sms_login

Manually: put the files in place

.claude/commands/phone_sms_login.md

Questions about phone_sms_login

How to install phone_sms_login in Claude Code?

Save the prompt file to .claude/commands/phone_sms_login.md.

What does phone_sms_login do?

It coordinates automated SMS login in Android apps using local trusted profiles without exposing credentials to the model.

What is required to run phone_sms_login?

You need a pre-configured, authorized local profile in device Settings and the exact Android package name of the target app.

Source text

phone_sms_login.md · Apache-2.0
Automatically log into an app only when the user explicitly asked for that login. Give its exact Android package. The host selects a device-local trusted profile containing the signed app identity, account, sender/service, native field/button mappings and logged-in account evidence. These private settings never enter model arguments/results. The user configures and authorizes the profile once in Settings; there is no per-login confirmation or manual parameter entry.

The host fills the configured account, listens before requesting one new SMS, strictly matches service and account, fills its code, clicks the final login button once (unless the app already submitted automatically), and verifies the registered logged-in account on-device. Only logged_in means success. It requires matching account evidence on the landing page, no remaining code/login controls or visible code, and local OCR confirmation. Missing permissions, profiles, trustworthy identity, native controls or success evidence require a truthful failure/unverified report and manual takeover, never a fabricated success.

After verified success native text observations resume with transient code redaction, so continue the user's authorized task. Phone images/previews remain local for this run. An unverified flow keeps its privacy protection. Do not obtain or resend codes through SMS apps, notifications, screenshots, shell, sandbox or MCP; do not ask for a code in chat. Payment, account recovery, registration, CAPTCHA and risk checks are outside this tool's scope. Unsupported profiles, WebViews, split fields, copied/work profiles and unattended/child/remote tasks stay manual. Disabling or editing/deleting a profile revokes its current attempt.

© wangzan101 · Apache-2.0 · wangzan101/Mika

Similar prompts

All prompts for Mobile →

From the same set132

The whole set →
notice_triage notice_triage — a prompt for Claude Code and ChatGPT categorizes phone notifications from a single app. It isolates incoming alert text to prevent prompt injection inside assistant workflows. GP ChatGPT ★ 9,488repo stars phone_type_text The phone_type_text Claude Code prompt enters a complete text string into a phone field in one call. It can target a field by label or coordinates. GP ChatGPT ★ 9,488repo stars stop_summary stop_summary — a prompt for Claude Code and ChatGPT that summarizes progress when an assistant is stopped midway. It turns session logs into a concise status report in five lines or fewer. GP ChatGPT ★ 9,488repo stars web_script The web_script Claude Code prompt runs JavaScript to handle several tasks on the current web page. It can read list entries, move through results, or fill multiple fields in one call. GP ChatGPT ★ 9,488repo stars notices_read notices_read — a Claude Code prompt that reads notifications from apps Mika can access. Ask what came in or get a digest for a day, week, or month. GP ChatGPT ★ 9,488repo stars channels Prompt for Claude Code and ChatGPT manages screen and channel selection between mobile apps and built-in browser. GP ChatGPT ★ 9,488repo stars handover The handover prompt for Claude Code and ChatGPT tells an agent how to complete authorized tasks and hand control back to the user. It covers actions that need a password, one-time code, or CAPTCHA. GP ChatGPT ★ 9,488repo stars notice_day The notice_day prompt for Claude Code turns a list of app notifications into a structured daily digest. GP ChatGPT ★ 9,488repo stars

Project sponsors

Companies that keep this analytics open