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/omergulcicek/omergulcicek.com/tanstack-querygit clone --depth 1 https://github.com/omergulcicek/omergulcicek.comWhat 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.00398 |
| Opus 5 | $0.00000 | $0.00199 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
tanstack-query scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
useQuery({ queryKey: ["posts"], queryFn: () => axios.get("/posts") }); What it actually says
TanStack Query
Constraints
- Structure: Use Query Key Factory (
src/features/[feature]/api/query-keys.ts). - Hooks: Create custom hooks for every query/mutation.
- Keys: Use
as const. Establish hierarchical structure (all -> lists -> details). - Signal: Pass
AbortSignalto the API function. - Invalidation: Invalidate relevant keys in mutation
onSuccess. - Pagination: Include
pageand filters in the query key.
Bans
useQueryinside components (Custom hooks are mandatory).- Manual string query keys.
- Using API responses without validation.
- Ignoring Loading/Error states.
Correct Implementation
// features/skills/hooks/use-get-skills.ts export const useGetSkills = (filters: object) => useQuery({ queryKey: skillKeys.list(filters), queryFn: ({ signal }) => getSkills(filters, signal), });
Incorrect Implementation
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.
- today First seen · 52 lines · 0 tokens per session scan A 2b402df87f54
tanstack-query is a cursor rule published in the GitHub repository omergulcicek/omergulcicek.com (15 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 398 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other cursor rules, from other repositories
js-and-ts
When writing JavaScript or TypeScript code, use this guide for JavaScript best practices and guidance.
jsx-and-tsx
When writing React code, use this guide for React best practices and guidance.
facades
When writing facade functions, use this guide for facade functions best practices and guidance.
new-component-implementation
Provides a systematic, research-driven workflow for implementing new Vibe components - for the @vibe/core library (located in "packages/core") - from initial research through final validation. Emphasizes studying existing patterns, following established conventions, and systematic progression through types, component…
base-components
Comprehensive guide for base components in @vibe/core library (BaseInput, BaseList, BaseListItem, InfoText, FieldLabel). Documents their usage patterns, accessibility requirements, form integration patterns, and what consumers need to provide for optimal accessibility and UX. These components serve as foundational…
component-internal-structure
This rule defines conventions for the internal structure of React components within the @vibe/core library (located in "packages/core" directory). Adhering to these conventions ensures consistency, readability, and maintainability across the codebase.