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 TanStack/devtools --skill devtools-productiongit clone --depth 1 https://github.com/TanStack/devtoolsWrote 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/tanstack/devtools/devtools-production)<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.
<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>- NVIDIA SkillSpector pass
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.00043 | $0.03602 |
| Opus 5.5 | $0.00017 | $0.01441 |
| Sonnet 5.5 | $0.00009 | $0.00720 |
| Haiku 4.5 | $0.00004 | $0.00360 |
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.
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:
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.
- 23d ago Changed · +22 lines 7dfe713dac6d
- 1mo ago First seen · 463 lines · 43 tokens per session scan A 4ce57a776bff
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.
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 …
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.
zustand-docs
Zustand — small, fast, scalable state management for React. Store creation, hooks, middleware, TypeScript.
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.
react-patterns
Idiomatic React — hooks, composition, and clear state boundaries. Use when writing or reviewing React components.
remotion-conventions
Programmatic video with Remotion — compositions, timing, and rendering. Use when building Remotion videos.