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 rules/packmindhub/packmind/standard-tanstack-query-key-managementgit clone --depth 1 https://github.com/PackmindHub/packmindWhat 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.00000 | $0.00231 |
| Opus 5 | $0.00000 | $0.00115 |
| Sonnet 5 | $0.00000 | $0.00046 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
standard-tanstack-query-key-management 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.
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
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.
- 2d ago First seen · 16 lines · 0 tokens per session scan A c700a7183c37
standard-tanstack-query-key-management is a cursor rule published in the GitHub repository PackmindHub/packmind (306 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 231 tokens. 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 cursor rules, from other repositories
project
Core project context for ai-context-kit.
cursor-project-rule
Project Spine operating contract for "Ledger API".
project-spine-apps-web
Project Spine scoped guidance for "apps/web".
project-spine-packages-ui
Project Spine scoped guidance for "packages/ui".
cursorrules
Cursor rule "cursorrules" from googlarz/agents-sync, covering .cursorrules — managed by agents-sync v1.0.0, language: typescript / next.js 14 and run tests: npm test.
openai-agents-overview
Comprehensive reference for building with the OpenAI Agent SDK.