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.
git 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/rules/pingdotgg/t3code/cursor-cloud)<a href="https://agentmods.dev/rules/pingdotgg/t3code/cursor-cloud"><img src="https://agentmods.dev/badge/rules/pingdotgg/t3code/cursor-cloud/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/rules/pingdotgg/t3code/cursor-cloud"><img src="https://agentmods.dev/badge/rules/pingdotgg/t3code/cursor-cloud.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.01325 | $0.01325 |
| Opus 5.5 | $0.00530 | $0.00530 |
| Sonnet 5.5 | $0.00265 | $0.00265 |
| Haiku 4.5 | $0.00133 | $0.00133 |
Grade A, and why
cursor-cloud 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 11d 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
1 near-identical copy found in the catalogue:
- cursor-cloud — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Cloud specific instructions
These notes apply only to Cursor Cloud agents (kept out of the shared AGENTS.md since T3 Code is
developed in many places). They cover the pre-provisioned VM environment and non-obvious run caveats.
Toolchain
Pre-installed and wired into login shells (~/.bashrc/~/.profile): Node 24 (via nvm), the global
vp (Vite+) CLI, and its bundled pnpm. vp is the package manager + task runner for this repo
(vp i, vp check, vp run typecheck, vp test, vp run --filter <pkg> <script>).
- Node gotcha: the base image also ships an older Node on
/exec-daemonthat wins onPATHin non-login shells. Run commands in a login shell (bash -lc '...') or prepend$HOME/.nvm/versions/node/v24.13.1/binso Node 24 (engines.node: ^24.13.1) is used. vp checkalso runs the formatter (not just lint); markdown edits must be formatter-clean. Runvp check --fixbefore committing.
Running the web app
npm run dev(from repo root) starts contracts (watch), web (Vite, port 5733), and the server (node --watch, port 13773) together, auto-wiringVITE_HTTP_URL/VITE_WS_URL. Usenpm run dev:server/npm run dev:webfor one side. If base ports are taken it auto-offsets to the next free pair, so read the actual ports from stdout. Avoid productionbuild/startin dev.- Auth/pairing: the server is unauthenticated by default and prints a pairing URL to stdout on startup
(e.g.
http://localhost:5733/pair#token=XXXX). Open that URL in the browser to pair before the web UI can talk to the server. Server state (SQLite, auth, projects) lives under~/.t3(T3CODE_HOME); multiplenpm run devinstances bind different ports but share that same DB. - Agent providers are external CLIs (
codex,claude,cursor-agent,opencode) probed onPATH. Without one installed the UI loads but no agent can run. Claude Code (npm i -g @anthropic-ai/claude-code) works headlessly usingANTHROPIC_API_KEYfrom the environment (the server forwardsprocess.envto the child; no interactiveclaude auth loginneeded). Provider probing runs at startup and refreshes roughly every 5 minutes — restart the dev server to pick up a newly installed provider CLI immediately.
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.
- 11d ago Changed · -2 tokens per session 96ac2fa4650c
- 1mo ago First seen · 73 lines · 1,327 tokens per session scan A 9f8540c10651
cursor-cloud is a cursor rule published in the GitHub repository pingdotgg/t3code (28,167 stars, last pushed today), licensed MIT. It adds 1,325 tokens to every session, about $0.0053 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 cursor rules, from other repositories
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.