More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Phone SSH Lab: Termux File Route

    1

    Reach your Android phone's files on demand: Termux SSH on a fixed port over Tailscale, key-only login, hash-verified pulls and pushes.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Phone SSH Lab: Termux File Route

    Phone SSH Lab: Termux File Route

    Example session with this skill installed

    I need my agent to pull screen recordings off my Android phone for review and push test builds back to Download, repeatably, without re-pairing adb every session. Set up the route with this skill and show me how one session runs, including how you prove the files arrived intact.

    • Read your context and instructions
    • Compiled the phone ssh lab

    Setup, one time, on the phone: install Termux (F-Droid build, not the stale Play Store one) and Tailscale signed into the same tailnet. Run the setup script in Termux: it installs openssh and rsync, runs termux-setup-storage, writes the dedicated public key into authorized_keys, writes a Termux:Boot autostart that launches sshd on fixed port 8022, key-only, and starts sshd. Tap Allow on the storage prompt. The script prints the Termux username (form u0_aNNN); that single value becomes the helper default. No passwords exist in this design, so none change hands.

    One session, run against the route after it passed its first-run verification: standing conditions checked first — Tailscale connected, sshd running. df shows 1.7G free on a 221G phone, noted before pushing anything. ls on ~/storage/shared/Movies lists the recording at its expected size. Pull brings the 40 MB file down; md5sum runs on both sides and the hashes match exactly, so the pull is reported verified, not just finished. The 96 MB test build pushes to /sdcard/Download/; a follow-up ls shows the exact byte size and a remote md5 matches the local build. Only then is the delivery called confirmed.

    If the first ls had failed, the session stops there and reports which standing condition broke — Tailscale off or sshd down — instead of retrying transfers against a dead route. That discipline, plus the four-step verification (list, hash-matched pull, push-read-delete round trip, recorded baseline), is what makes the route trustworthy the tenth time, not just the first.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    If your agent works with your phone, you already know the adb routine: wireless debugging ports that change between sessions, pairing codes that expire in minutes, and file transfers you cannot prove arrived intact. This skill replaces that with a route built once and reused forever: Termux running sshd on fixed port 8022, key-only authentication with a dedicated keypair, a Termux:Boot autostart so the service survives reboots, and Tailscale as the transport. One helper gives you listing, pull, push, and remote shell through a single command surface.

    Inside: the one-time phone setup (about fifteen minutes, done by the phone's owner, ending with a single username value changing hands — no passwords ever); a route-selection table that says plainly when SSH is right, when adb is right, and why app pairings cannot do file work at all; a session checklist covering the two standing conditions that cause nearly every failure (Tailscale off, sshd not restarted after a reboot); a four-step first-run verification recipe — list, pull with identical md5 on both sides, push and read back and delete, record the baseline; a worked example of a full delivery round trip; a symptom-to-first-move troubleshooting table; and the gotchas learned live, including the nearly full phone that truncates pushes while looking like a network bug, the tilde-quoting bug that silently breaks listings, and the changed-host-key stop sign you must never bypass.

    Every transfer is verified by hash or listing on the receiving side. Exit code zero is never accepted as proof.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.

    Scope is the Android sandbox: Termux home plus all of /sdcard. Other apps' private data directories are not reachable — that is a platform limit, not a configuration problem. The route does files only: no screen control, no install automation, no logcat. Android battery management can stop Termux in the background, after which someone must reopen it and restart sshd. Transfers depend on Tailscale being connected on the phone; when it is off, the honest output is a named failure, not a workaround.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Permissions

    No special permissions declared or detected

    Listed24 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    Reach your Android phone's files on demand: Termux SSH on a fixed port over Tailscale, key-only login, hash-verified pulls and pushes.

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use Phone SSH Lab: Termux File Route on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    New in Mobile Development