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 prepare-releasegit 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/prepare-release)<a href="https://agentmods.dev/skills/pingdotgg/t3code/prepare-release"><img src="https://agentmods.dev/badge/skills/pingdotgg/t3code/prepare-release/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/prepare-release"><img src="https://agentmods.dev/badge/skills/pingdotgg/t3code/prepare-release.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.00153 | $0.05018 |
| Opus 5.5 | $0.00061 | $0.02007 |
| Sonnet 5.5 | $0.00031 | $0.01004 |
| Haiku 4.5 | $0.00015 | $0.00502 |
Grade A, and why
prepare-release 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 yesterday.
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 — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare a release
This session is the coordinator of the convergence loop in AGENTS.md ("The convergence loop: nuke → test → census → fix-fleet"). You own the clean slate, the test runs, triage, type-checking, the census, and the PRs. Fix agents own one service each. The user merges; you never do.
Each provider in scope converges with the harden skill
(.agents/skills/harden/SKILL.md): its loop, root-cause order, isolation
rules and the provider-bug patterns it lists all apply here. This skill adds
the release-wide pieces around it: the clean slate, the plan across
providers, the fix fleet, and the PRs. When the user only asks to harden a
provider, use the harden skill instead of this one.
The arguments name the scope: providers (aws cloudflare gcp …) or all. With
no arguments, propose a scope (default: unit + local + every provider:* live
tag) and confirm it together with the nuke in a single question. Nuking the
testing account is destructive — always get an explicit go-ahead first.
0. Preflight
Start from a clean, up-to-date main in this worktree, on a fresh branch:
git status # must be clean; never git stash
git fetch origin main && git checkout -b release/prep-$(date +%Y-%m-%d) origin/main
git submodule update --init -- submodules/distilled
pnpm install
bun --version # must be 1.3.13 — 1.4 fails every file at collection
# if not: mkdir -p /tmp/bun1313 && (cd /tmp/bun1313 && npm i --no-save [email protected])
# export PATH=/tmp/bun1313/node_modules/.bin:$PATH (prefix every pnpm test with this)
node -v # alchemy CLI needs >= 24.11.1 and pnpm wants 24.x — node 25
# makes pnpm print a [WARN] that breaks scripts/ensure-built.ts. If not 24.11+:
# mkdir -p /tmp/node24 && (cd /tmp/node24 && npm i --no-save node@24)
# export PATH=/tmp/node24/node_modules/.bin:$PATH
# Put these PATH exports + `set -a; source .env; set +a` in /tmp/release/env.sh and
# source it before every command — env doesn't persist between shell calls.
set -a; source .env; set +a # Cloudflare creds (pnpm download:env if missing)
aws sso login # AWS live + nuke ride the SSO session
mkdir -p /tmp/release
pnpm exec tsrs -b # REQUIRED before live runs: emits distilled lib/
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.
- yesterday First seen · 381 lines · 153 tokens per session scan A 1909c29495a6
prepare-release is a skill published in the GitHub repository pingdotgg/t3code (46,669 stars, last pushed today), licensed MIT. It adds 153 tokens to every session and 5,018 once invoked, about $0.0006 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-11-04.
Other skills, from other repositories
tadado-release
A release checklist for the Tadado2 repository. It defines how to test, package, commit, push, tag, publish a GitHub Release, and synchronize the local skill files.
release
Release preparation workflow - security audit → E2E tests → review → changelog → docs.
release-pr-quality-gate
Build an AgentWorks release or pull-request browser quality gate over saved suites and exact build identity. Use when a merge, deployment, or promotion needs an auditable QA decision.
dev-ship
Fechamento de feature — verificação goal-backward antes de declarar pronto. Roda Must-Haves do PLAN.md, executa o demo script, revisa o diff completo procurando bugs e restos (debug logs, TODOs, código morto), passa lente de segurança nos arquivos tocados, escreve SUMMARY.md e arquiva o plano. Use quando o usuário…
release-validation
The final "Green Light". Checks all test suites (Unit, Int, E2E) and third-party reports.
test-next-release
Smoke-test the @next npm release against the petstore example — installs globally, sets up session auth, and verifies all CRUD operations work end-to-end.