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-app/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-app)<a href="https://agentmods.dev/skills/pingdotgg/t3code/test-t3-app"><img src="https://agentmods.dev/badge/skills/pingdotgg/t3code/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/pingdotgg/t3code/test-t3-app"><img src="https://agentmods.dev/badge/skills/pingdotgg/t3code/test-t3-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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 33 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.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 1mo 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.
- 1mo ago Changed · -49 lines · -52 tokens per session 7ebcf3fdcf74
- 1mo ago First seen · 91 lines · 100 tokens per session scan A 6e2062ea00e2
test-t3-app is a skill published in the GitHub repository pingdotgg/t3code (29,151 stars, last pushed today), 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-08-30.
Other skills, from other repositories
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".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
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.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…