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 agentmods add skills/suxrobgm/jobpilot/tanstack-form-compositionnpx skills add suxrobGM/jobpilot --skill tanstack-form-compositiongit clone --depth 1 https://github.com/suxrobGM/jobpilotWrote 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/suxrobgm/jobpilot/tanstack-form-composition)<a href="https://agentmods.dev/skills/suxrobgm/jobpilot/tanstack-form-composition"><img src="https://agentmods.dev/badge/skills/suxrobgm/jobpilot/tanstack-form-composition.svg" alt="Measured on agentmods" 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 | $0.00158 | $0.02747 |
| Opus 5 | $0.00079 | $0.01373 |
| Sonnet 5 | $0.00032 | $0.00549 |
| Haiku 4.5 | $0.00016 | $0.00275 |
Grade A, and why
tanstack-form-composition 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 4d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TanStack Form → composition API migration
Convert a React project using @tanstack/react-form from raw useForm +
prop-drilled field wrappers + an any-erased form type to the createFormHook
composition API. The payoff: typed field names/values, deletion of the erased
form type and every as unknown as <ErasedForm> cast, and bound field components
consumed as field.TextField instead of <FieldWrapper form={form} name=… />.
This is for the React adapter. Solid/Vue/Angular have the same API shape with different hook names - the concepts below port directly.
When this applies
The codebase has most of these symptoms:
- An erased form type alias, e.g.
type AnyForm = ReactFormExtendedApi<any,any,…>(12anygenerics), used as a prop type and reached viaform as unknown as AnyForm. - Field components that accept
form+nameprops and internally render<form.Field name={name}>…</form.Field>. - Shared "section" components that receive the whole
formas a prop and are reused across multiple parent forms (e.g. a settings form and an onboarding wizard). - Helper functions that take the
formand callgetFieldValue/setFieldValue.
If the project does not yet use @tanstack/react-form, stop - this skill
migrates an existing TanStack Form codebase; it does not introduce the library.
Method
Work in four phases. Do recon fully before editing; build the shared infra once; then migrate call sites; then delete the erased type and verify. On a large repo, migrate one simple form end-to-end first as a reference, then fan out.
Phase 0 - Recon
Confirm the version and map the blast radius. Run (adapt paths):
- Dependency: grep
package.jsonfor@tanstack/react-form(need v1+;createFormHook,createFormHookContexts,withFormare stable in v1). - Form-creation sites: search
useForm(. - The erased type + casts: search the alias name and
as unknown as. - Existing field wrappers: the directory of components taking
form/nameprops. - Shared sections: components whose props include the erased form type.
- Form-consuming helpers: functions whose parameter is the erased form type.
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.
- 4d ago First seen · 268 lines · 158 tokens per session scan A dbc3ca56931c
tanstack-form-composition is a skill published in the GitHub repository suxrobGM/jobpilot (60 stars, last pushed 14d ago), licensed MIT. It adds 158 tokens to every session and 2,747 once invoked, about $0.0008 per session on Opus 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
react-frontend
React, TypeScript, and Next.js patterns for frontend development. Use when building React components, managing state, fetching data, optimizing performance, or working with Next.js App Router. Covers React 18-19, hooks, Server Components, and type-safe patterns.
stitch-nextjs-components
Converts a Stitch screen, a local HTML file, or a URL into production-ready Next.js 15 App Router components — Server vs Client split, dark mode via CSS variables, TypeScript strict, ARIA, and responsive mobile-first layout. Only the Stitch route needs an API key.
react-patterns
React + TypeScript component and hook standards. TRIGGER when: creating components, custom hooks, or reviewing React code. SKIP: visual styling and theme tokens (use mui-styling); global store design (use state-management).
nextjs-patterns
Next.js App Router — Server Components, Actions, streaming, caching. Use when building or migrating Next.js apps.
senior-frontend
Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.
migrate
Code migration assistant — upgrade frameworks, convert languages, modernize patterns.