T3 Code is an app for controlling AI coding agents running on a user's computer through mobile, web, and desktop interfaces. Developers use it to work remotely with supported agents such as Codex, Claude Code, Cursor, Grok Build, OpenCode, and Antigravity. The catalogue add-ons support the T3 Code workflow.
Borrowing it
Nothing to install: this file belongs to pingdotgg/t3code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pingdotgg/t3code/main/.agents/skills/test-t3-mobile/SKILL.mdgit clone --depth 1 https://github.com/pingdotgg/t3codeWrote 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/pingdotgg/t3code/test-t3-mobile)<a href="https://agentmods.dev/skills/pingdotgg/t3code/test-t3-mobile"><img src="https://agentmods.dev/badge/skills/pingdotgg/t3code/test-t3-mobile/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.
<a href="https://agentmods.dev/skills/pingdotgg/t3code/test-t3-mobile"><img src="https://agentmods.dev/badge/skills/pingdotgg/t3code/test-t3-mobile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Rogue Agent · line 39 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00046 | $0.00691 |
| Opus 5.5 | $0.00018 | $0.00276 |
| Sonnet 5.5 | $0.00009 | $0.00138 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
test-t3-mobile 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 20d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test T3 Mobile
Open the device
Call device_list, then device_open with the selected host and device IDs.
T3 boots the device and shows its live stream in the Device panel. Follow its
returned quickStart, using the exact agentDevice.command and all targetArgs
on every operation. Use device_screenshot to inspect the screen.
If T3 device tools or the selected device are unavailable, report the blocker and stop verification. Do not install or switch to another automation system.
Use an isolated backend
Reuse this task's healthy backend. Otherwise run vp run dev from the
repository root, retain its terminal session, and read the actual backend port
from the dev-runner output. Use the worktree's ignored .t3 state. Never run
against ~/.t3/userdata. The Browser panel is not required for this workflow.
Test with meaningful project and thread data. Read the shared SQLite fixture reference only when inspecting or seeding SQLite. Stop the test server before fixture writes.
Launch T3 Code Dev
From the checkout being tested on the selected device host, run:
node scripts/mobile-native-client.ts ensure <ios|android> <device-id>
This reuses a matching native client or builds and installs one. Authorized mobile verification includes that build step unless the user prohibits it.
Start vp run dev:client from apps/mobile, or reuse a healthy Metro belonging
to this checkout. Open its printed development-client URL with AgentDevice
open com.t3tools.t3code.dev <url> and all returned target arguments.
The device must be able to reach both Metro and the isolated backend.
Append &disableAutoLaunch=1&disableFab=1 to the development-client URL query
when developer chrome would obscure screenshots or taps; the SDK 58 dev client
applies these preferences before the app loads.
Pair and verify
Use the helper from the repository root, with the returned executable and target
arguments stored in agent_device_command and the Bash array
agent_device_target_args:
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 20d ago Changed · +3 lines 6bb361594faa
- 1mo ago Changed · -125 lines · -49 tokens per session 0835837f5852
- 1mo ago Changed · +2 lines 5662e7aa4f2b
- 1mo ago First seen · 189 lines · 95 tokens per session scan A 28e170f93ec9
test-t3-mobile is a skill published in the GitHub repository pingdotgg/t3code (29,151 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 691 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
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.
eas-simulator
Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas simulator to…
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…