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.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add pingdotgg/t3code --skill test-developmentgit 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-development)<a href="https://agentmods.dev/skills/pingdotgg/t3code/test-development"><img src="https://agentmods.dev/badge/skills/pingdotgg/t3code/test-development/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-development"><img src="https://agentmods.dev/badge/skills/pingdotgg/t3code/test-development.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.00042 | $0.00210 |
| Opus 5.5 | $0.00017 | $0.00084 |
| Sonnet 5.5 | $0.00008 | $0.00042 |
| Haiku 4.5 | $0.00004 | $0.00021 |
Grade A, and why
test-development 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 10d 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- test-development — 100% identical, 0 lines differ
- test-development — 100% identical, 22 lines differ
- test-development — 100% identical, 22 lines differ
- test-development — 100% identical, 0 lines differ
What it actually says
Choose branches from the task's acceptance criteria before editing:
- Runtime behavior: The intended result is observable when code executes. Read runtime.md.
- Compiler behavior: The intended result is TypeScript accepting, rejecting, or inferring a consumer expression in a particular way. Read types.md.
An exported signature alone is validated by pnpm check; it enters the compiler
branch only when its inference, assignability, rejection, overload selection, or
displayed type is part of the task. Some changes require both branches because
they independently change runtime and compiler behavior.
The task is complete when each intended behavior in scope has the relevant focused coverage, targeted tests pass, and applicable root checks pass or are reported as not runnable.
What ships with it
3 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.
- 10d ago Changed · +8 lines · +9 tokens per session b9eeb39cf3ea
- 27d ago First seen · 14 lines · 33 tokens per session scan A ded4ade9f625
test-development is a skill published in the GitHub repository pingdotgg/t3code (27,790 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 210 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-09-19.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
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.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.