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 Casper-Studios/casper-marketplace --skill tanstack-react-query-best-practicesgit clone --depth 1 https://github.com/Casper-Studios/casper-marketplaceWrote 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/casper-studios/casper-marketplace/tanstack-react-query-best-practices)<a href="https://agentmods.dev/skills/casper-studios/casper-marketplace/tanstack-react-query-best-practices"><img src="https://agentmods.dev/badge/skills/casper-studios/casper-marketplace/tanstack-react-query-best-practices.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.1 | $0.00037 | $0.00613 |
| Opus 5 | $0.00018 | $0.00307 |
| Sonnet 5 | $0.00007 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
tanstack-react-query-best-practices 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TanStack React Query Best Practices
Treat server data as cache-backed asynchronous state with an explicit owner, identity, and view boundary; the outcome is reliable loading and error handling plus focused updates after writes.
Library Sources
- GitHub repository ID:
TanStack/query - Context7 library ID:
/tanstack/query - DeepWiki repository ID:
TanStack/query
Use Context7 for current documentation and DeepWiki for implementation details.
References
Read the references that apply to the current task before writing or reviewing TanStack Query code.
- Let TanStack Query own server-request lifecycle and cache identity.
- Let TanStack Query own request lifecycle rather than duplicating it with effects and local state.
- Put every response-changing request input in cache identity so distinct results never reuse one entry.
- Read request inputs exclusively from the query function's context argument, never from captured request variables.
- Preserve absent identifiers and disable the request instead of fabricating a record key.
- Partition visibility-sensitive cached data by actor identity without exposing credentials in keys.
- Resolve query status before presentation consumes data.
- Resolve query status at a Loader and Inner boundary, keeping presentation free of optional data and transport state.
- Publish query identity through loader prop contracts while resolved components receive non-null data.
- Destructure only consumed query fields so dependencies and props express semantic needs.
- Keep mutation data, callbacks, and cache updates scoped to each operation.
- Consume named mutation result fields because the complete
useMutationresult is not referentially stable. - Pass changing operation input through mutation variables, not a mutation hook's construction closure.
- Parse user-controlled values before mutation invocation.
- Separate mutation callback lifecycles by putting every-invocation policy in the definition and mounted UI consequences at the call site instead of aggregate-status effects.
- Invalidate the narrow stale entry identified by successful variables.
- Consume named mutation result fields because the complete
What ships with it
15 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.
- agents/openai.yaml 133 B
- LICENSE.txt 16 KB
- references/absent-identifiers.md 1.6 KB
- references/actor-identity-and-secrets.md 1016 B
- references/cache-identity.md 1.7 KB
- references/loader-and-inner.md 1.8 KB
- references/loader-prop-contracts.md 1000 B
- references/mutation-callback-lifecycle.md 1.7 KB
- references/mutation-form-integration.md 1.2 KB
- references/mutation-invalidation.md 979 B
- references/mutation-result-destructuring.md 1.4 KB
- references/mutation-variables.md 916 B
- references/query-function-inputs.md 1.8 KB
- references/request-ownership.md 2.0 KB
- references/result-destructuring.md 1.3 KB
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 Changed · +3 lines · -45 tokens per session ff7688d2e3ce
- 6d ago First seen · 39 lines · 82 tokens per session scan A 97b17738eb06
tanstack-react-query-best-practices is a skill published in the GitHub repository Casper-Studios/casper-marketplace (12 stars, last pushed 2d ago), licensed MPL-2.0. It adds 37 tokens to every session and 613 once invoked, about $0.0002 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-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
assistant-ui-primitives
Guide for assistant-ui UI primitives - ThreadPrimitive, ComposerPrimitive, MessagePrimitive. Use when customizing chat UI components.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…