packmind packmind-tanstack-query-key-management.instructions.md

A set of coding rules for organizing TanStack Query cache keys. TanStack Query is a tool that stores server data in a cache, and these keys let code find related cached data by matching parts from left to right.

In plain words
What is it for?
Use it when defining query and mutation keys, placing them in domain-specific files, and invalidating related cached queries after successful updates.
Why use it?
It reduces missed or overly broad cache invalidations when data changes. It also keeps key definitions in one place and helps avoid unwanted dependencies between parts of the application.

Instructions file for GitHub Copilot

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.

agentmods
npx agentmods add instructions/packmindhub/packmind/packmind-tanstack-query-key-management
Clone the repo
git clone --depth 1 https://github.com/PackmindHub/packmind

Made for: GitHub Copilot.

Per session 227 This file is loaded in full into every session.
When invoked 227 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00227 $0.00227
Opus 5 $0.00113 $0.00113
Sonnet 5 $0.00045 $0.00045
Haiku 4.5 $0.00023 $0.00023

Measured 2d ago against content hash 33b13b9dbea9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

packmind packmind-tanstack-query-key-management.instructions.md 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 2d 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.

apps/frontend/.github/instructions/packmind-tanstack-query-key-management.instructions.md · 15 lines

What it actually says

Standard: TanStack Query Key Management

TanStack Query uses prefix matching to invalidate cached queries, matching keys from left to right like a file path. Properly structured query keys enable efficient cache invalidation at any scope lev... :

  • Define base query key arrays as const to enable precise invalidation patterns and avoid duplication
  • Define domain query scope as a separate const outside enum to maintain clear separation between scope and operations
  • Define query keys in a dedicated queryKeys.ts file in the domain's api folder for centralized management
  • Follow hierarchical query key structure: organization scope, domain scope, operation, then identifiers for consistent invalidation patterns
  • In mutation onSuccess, invalidate every affected sibling query-key scope; prefix matching cannot bridge siblings
  • Limit cross-domain imports to only query key constants and enums to prevent runtime coupling and circular dependencies
  • Use query invalidation with prefix matching from key start in correct hierarchical order

Full standard is available here for further request: TanStack Query Key Management

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. 2d ago First seen · 15 lines · 227 tokens per session scan A 33b13b9dbea9

Subscribe to this mod's changes

packmind packmind-tanstack-query-key-management.instructions.md is an instructions file published in the GitHub repository PackmindHub/packmind (306 stars, last pushed 5d ago), licensed Apache-2.0. It adds 227 tokens to every session, about $0.0011 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.