Local Studio is a local-first control panel for running, managing, and using self-hosted large language model backends such as vLLM, SGLang, llama.cpp, and ExLlama. It lets users launch models, monitor GPU and runtime state, chat through OpenAI-compatible endpoints, and run agent sessions from a desktop or connected mobile device. The catalogue skills and instruction support agent workflows with Local Studio and its controllers.
Borrowing it
Nothing to install: this file belongs to sybil-solutions/local-studio. 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/sybil-solutions/local-studio/main/.agents/skills/test-t3-mobile/SKILL.mdgit clone --depth 1 https://github.com/sybil-solutions/local-studioWrote 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/sybil-solutions/local-studio/test-t3-mobile)<a href="https://agentmods.dev/skills/sybil-solutions/local-studio/test-t3-mobile"><img src="https://agentmods.dev/badge/skills/sybil-solutions/local-studio/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/sybil-solutions/local-studio/test-t3-mobile"><img src="https://agentmods.dev/badge/skills/sybil-solutions/local-studio/test-t3-mobile.svg" alt="Reviewed on agentmods" width="80" 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.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 9d 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.
- 9d ago First seen · 69 lines · 46 tokens per session scan A 6bb361594faa
test-t3-mobile is a skill published in the GitHub repository sybil-solutions/local-studio (1,833 stars, last pushed 10d ago), 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-10-13.
Other skills, from other repositories
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.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
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…
ios-simulator-skill
Build, test, and drive iOS apps in the Simulator with 30 token-efficient scripts. Use when asked to build or test an Xcode project, launch an app on a simulator, tap/type/swipe through its UI by accessibility label, take screenshots or visual diffs, audit accessibility, read logs or diagnose hangs, or manage…
asc-shots-pipeline
Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (asc screenshots frame), and screenshot upload (asc screenshots upload). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition…