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 package-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/package-development)<a href="https://agentmods.dev/skills/pingdotgg/t3code/package-development"><img src="https://agentmods.dev/badge/skills/pingdotgg/t3code/package-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/package-development"><img src="https://agentmods.dev/badge/skills/pingdotgg/t3code/package-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.00031 | $0.00379 |
| Opus 5.5 | $0.00012 | $0.00152 |
| Sonnet 5.5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
package-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 27d 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:
- package-development — 100% identical, 0 lines differ
- package-development — 100% identical, 0 lines differ
- package-development — 100% identical, 0 lines differ
- package-development — 100% identical, 0 lines differ
What it actually says
Treat package work as a registration change, not a directory copy.
Workflow
- Inspect the closest package in the same family. Classify publication status, runtime, test environment, platform support, barrels, and dependency shape. Justify each proposed file by precedent or an explicit repository need. Continue when every proposed file is justified.
- Create or move only required source, test, TypeScript, and manifest files. When manifest dependencies change, read dependencies.md and classify every entry by role. Continue when pnpm discovers the intended name and manifests reference no absent file.
- Read registration.md. Classify every registration surface as applicable or not applicable and update every applicable surface. Continue when every surface is classified and old references are explained.
- For a published package, read publishing.md and verify its development and packed surfaces.
- Run codegen when the package owns generated barrels, then inspect generated sections rather than editing them manually. Continue when generated sections match source modules without manual edits.
- Run focused package tests and scripts plus applicable root checks. Include public API type tests when applicable. For published packages, build and dry pack the package as described in publishing.md. Continue when focused and root checks pass and the packed surface is intended.
- Apply root changeset, generated-file, documentation, and workflow routing.
The task is complete when package discovery, registration, generated output, validation, packed output, and changeset routing are all verified or reported as not applicable.
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.
- 27d ago First seen · 36 lines · 31 tokens per session scan A 0778f74bc497
package-development is a skill published in the GitHub repository pingdotgg/t3code (27,790 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 379 once invoked, about $0.0001 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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…