devtools-production

devtools-production is a skill for Claude Code, Codex from TanStack/devtools. It costs 43 tokens per session (3,602 once invoked), scanned A, original, MIT.

Guidance for keeping TanStack Devtools available during development while removing it from production builds when appropriate. It covers Vite projects and other setups with different production strategies.

In plain words
What is it for?
Use it when configuring TanStack Devtools dependencies, imports, Vite build settings, or production behavior.
Why use it?
It prevents development-only tools from increasing the size or contents of a released application.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when configuring TanStack Devtools dependencies, imports, Vite build settings, or production behavior.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tanstack/devtools/devtools-production
Install

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.

Any agent
npx skills add TanStack/devtools --skill devtools-production
Clone the repo
git clone --depth 1 https://github.com/TanStack/devtools

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for devtools-production

README.md
[![agentmods](https://agentmods.dev/badge/skills/tanstack/devtools/devtools-production/github.svg)](https://agentmods.dev/skills/tanstack/devtools/devtools-production)
Your own site
<a href="https://agentmods.dev/skills/tanstack/devtools/devtools-production"><img src="https://agentmods.dev/badge/skills/tanstack/devtools/devtools-production/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.

agentmods 80×15 button for devtools-production

Your own site · 80×15
<a href="https://agentmods.dev/skills/tanstack/devtools/devtools-production"><img src="https://agentmods.dev/badge/skills/tanstack/devtools/devtools-production.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,602 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.03602
Opus 5.5 $0.00017 $0.01441
Sonnet 5.5 $0.00009 $0.00720
Haiku 4.5 $0.00004 $0.00360

Measured 23d ago against content hash 7dfe713dac6d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

devtools-production 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 23d 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.

packages/devtools/skills/devtools-production/SKILL.md · 485 lines

How it starts

The opening of the file, as written. The whole thing — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.

TanStack Devtools Production Handling

Prerequisite: Read the devtools-app-setup skill first. The initial setup decisions (framework adapter, Vite plugin, dependency type) directly determine which production strategy applies.

How Production Stripping Works

TanStack Devtools has two independent mechanisms for keeping devtools out of production bundles. Understanding both is essential because they serve different project types.

Mechanism 1: Vite Plugin Auto-Stripping (Vite projects)

The @tanstack/devtools-vite plugin includes a sub-plugin named @tanstack/devtools:remove-devtools-on-build. When removeDevtoolsOnBuild is true (the default), this plugin runs during vite build and any non-serve command where the mode is production.

It uses oxc-parser to parse every source file, find imports from these packages, and remove them along with any JSX elements they produce:

  • @tanstack/react-devtools
  • @tanstack/preact-devtools
  • @tanstack/solid-devtools
  • @tanstack/vue-devtools
  • @tanstack/svelte-devtools
  • @tanstack/angular-devtools
  • @tanstack/devtools

The stripping is AST-based. It removes the import declaration, then finds and removes any JSX elements whose tag name matches one of the imported identifiers. It also traces plugin references inside the plugins prop array and removes their imports if they become unused.

Source: packages/devtools-vite/src/remove-devtools.ts

This means for a standard Vite project, the default setup from devtools-app-setup already handles production correctly with zero additional configuration:

// This import and JSX element are completely removed from the production build
import { TanStackDevtools } from '@tanstack/react-devtools'

function App() {
  return (
    <>
      <YourApp />
      <TanStackDevtools
        plugins={
          [
            /* ... */
          ]
        }
      />
    </>
  )
}

Mechanism 2: Conditional Exports (package.json)

The @tanstack/devtools core package uses Node.js conditional exports to serve different bundles based on the environment:

Read the full file on GitHub · 485 lines

Changes

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.

  1. 23d ago Changed · +22 lines 7dfe713dac6d
  2. 1mo ago First seen · 463 lines · 43 tokens per session scan A 4ce57a776bff

Subscribe to this mod's changes

devtools-production is a skill published in the GitHub repository TanStack/devtools (506 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 3,602 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.

Related

Other skills, from other repositories

install-next

Installs and wires @rsc-boundary/next into a Next.js App Router app (dependencies, root layout provider, optional explicit markers). Use when the user wants to add RSC Boundary, integrate @rsc-boundary/next, or set up server/client boundary devtools in Next.js. The unscoped rsc-boundary package on npm is deprecated …

foxted/rsc-boundary · 82 tokens

install-start

Installs and wires the npm package @rsc-boundary/start into a TanStack Start app (dependencies, root route provider, optional explicit markers). Use when the user wants to add RSC Boundary to a TanStack Start / TanStack Router app, or set up server/client boundary devtools with TanStack.

foxted/rsc-boundary · 66 tokens

zustand-docs

Zustand — small, fast, scalable state management for React. Store creation, hooks, middleware, TypeScript.

pledgeandgrow/pledge-skills · 29 tokens

vite-browser-core-debug

Core troubleshooting workflow for Vue/React/Svelte Vite apps using vite-browser. Use this for first-pass debugging when the user reports broken UI behavior, wrong component state, router/store confusion, or a vague "page is broken" symptom and the dominant failure mode is not yet known.

MapleCity1314/vite-browser · 62 tokens

react-patterns

Idiomatic React — hooks, composition, and clear state boundaries. Use when writing or reviewing React components.

Cypsy1714/cchad · 25 tokens

remotion-conventions

Programmatic video with Remotion — compositions, timing, and rendering. Use when building Remotion videos.

Cypsy1714/cchad · 26 tokens