apollo-caching

apollo-caching is a cursor rule for Cursor from holtwood/awesome-cursorrules-zh. It costs 0 tokens per session (213 once invoked), scanned A, original, MIT.

Guidelines for using Apollo Client's built-in cache, which stores query results so an app can reuse them instead of requesting the same data again.

In plain words
What is it for?
Use them when building Apollo Client queries, mutations, subscriptions, or infinite-scroll lists in a frontend application.
Why use it?
They help reduce unnecessary network requests and keep the user interface aligned with data changed by mutations. They also explain how to handle changing data, subscriptions, polling, and paginated lists.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use them when building Apollo Client queries, mutations, subscriptions, or infinite-scroll lists in a frontend application.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/holtwood/awesome-cursorrules-zh/apollo-caching
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.

Clone the repo
git clone --depth 1 https://github.com/holtwood/awesome-cursorrules-zh

Made for: Cursor.

Wrote 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.

agentmods badge for apollo-caching

README.md
[![agentmods](https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/apollo-caching/github.svg)](https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/apollo-caching)
Your own site
<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/apollo-caching"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/apollo-caching/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for apollo-caching

Your own site · 80×15
<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/apollo-caching"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/apollo-caching.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 213 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00213
Opus 5 $0.00000 $0.00106
Sonnet 5 $0.00000 $0.00043
Haiku 4.5 $0.00000 $0.00021

Measured 7d ago against content hash 0dbf44f57149, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

apollo-caching 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 7d 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.

docs/rules/frontend/react/apollo-graphql/apollo-caching.mdc · 11 lines

What it actually says

  • 利用 Apollo Client 的缓存功能
    • 优先使用 Apollo Client 的规范化缓存(Normalized Cache)来存储和管理数据,减少不必要的网络请求。
    • 理解并配置 fetchPolicy,以优化数据获取策略,例如 cache-firstnetwork-onlycache-and-network 等。
    • 针对频繁变动的数据,考虑使用 no-cachecache-and-network 策略,并结合订阅(Subscriptions)或轮询(Polling)实现实时更新。
    • 对于列表数据,合理使用 offsetLimitPaginationcursorPagination 等策略来处理分页和无限滚动,确保缓存的有效性。
    • 在进行数据修改(如 Mutations)后,通过 update 函数或 refetchQueries 来及时更新缓存,保持UI与后端数据的一致性。
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. 7d ago First seen · 11 lines · 0 tokens per session scan A 0dbf44f57149

Subscribe to this mod's changes

apollo-caching is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (233 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 213 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-09-03.