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-app/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-app)<a href="https://agentmods.dev/skills/sybil-solutions/local-studio/test-t3-app"><img src="https://agentmods.dev/badge/skills/sybil-solutions/local-studio/test-t3-app/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-app"><img src="https://agentmods.dev/badge/skills/sybil-solutions/local-studio/test-t3-app.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.00048 | $0.00437 |
| Opus 5.5 | $0.00019 | $0.00175 |
| Sonnet 5.5 | $0.00010 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
test-t3-app 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.
What it actually says
Test T3 web and desktop
Use T3's built-in Browser panel for verification. If its tools are absent or the panel reports unavailable, explain the blocker and stop verification. Do not install or switch to another automation system. For native mobile testing, use test-t3-mobile.
Start the app
Reuse this task's healthy dev server. Otherwise run vp run dev from the
repository root and retain its terminal session. Use the worktree's ignored
.t3 state and read the actual ports and pairing URL from the dev-runner output.
Never run against ~/.t3/userdata or set VITE_HTTP_URL or VITE_WS_URL.
Test with meaningful project and thread data. Read references/sqlite-fixtures.md only when inspecting or seeding SQLite. Stop the test server before direct fixture writes.
Use the Browser panel
Call preview_status, then preview_open if the Browser panel is
closed. Navigate to the complete startup pairing URL once with
preview_navigate, then use preview_snapshot and T3's interaction tools.
If the token was consumed or expired, run node apps/server/src/bin.ts pair
for a fresh one. Keep using the same tab.
Verify and retain
Exercise the affected flow and capture the state that proves it works. Keep the server, state, and panel available while the user inspects or iterates. An assistant turn ending is not teardown. Stop only processes you started, using retained terminal sessions or captured PIDs.
When sharing is requested, start with vp run dev --share and give the user
a fresh complete pairing URL that you have not consumed. Keep other credentials
out of screenshots, commits, and replies.
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 · 42 lines · 48 tokens per session scan A 7ebcf3fdcf74
test-t3-app is a skill published in the GitHub repository sybil-solutions/local-studio (1,833 stars, last pushed 10d ago), licensed MIT. It adds 48 tokens to every session and 437 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
browser-qa
Testing web apps through a real browser: reconnaissance before acting, selector discovery, state capture, console errors and screenshot evidence. Use on a web surface end to end, or to reproduce a front-end bug.
nyx-ui-screenshots
Regenerate the README UI screenshots for nyx-local-ai from the browser harness — build the webview, serve the harness scenes, capture and crop the images into docs/. Use when the UI changed visibly, when the user asks to update screenshots, or before a release with UI changes.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".