react-graphql-apollo-client-cursorrules-prompt-file

react-graphql-apollo-client-cursorrules-prompt-file is a cursor rule for Cursor from PatrickJS/awesome-cursorrules. It costs 242 tokens per session, scanned A, original, CC0-1.0.

A set of Cursor coding rules for React applications that fetch data from GraphQL APIs using Apollo Client. GraphQL is a way to request specific data from an API, while Apollo handles fetching, caching, and updates.

In plain words
What is it for?
Use it when creating GraphQL queries, mutations, reusable fragments, custom Apollo hooks, caching, and error boundaries in a React app.
Why use it?
It provides shared conventions for queries and data changes, including loading and error handling, so API code is easier to organize.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: mentions Cursor.

Good fit Use it when creating GraphQL queries, mutations, reusable fragments, custom Apollo hooks…

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/patrickjs/awesome-cursorrules/react-graphql-apollo-client-cursorrules-prompt-file
About the project

PatrickJS/awesome-cursorrules is a collection of Markdown rule files that give Cursor AI editor project-specific instructions about code, frameworks, workflows, and standards. Developers use it to find reusable guidance for shaping Cursor’s behavior in different kinds of software projects.

PatrickJS/awesome-cursorrules · 40,732 stars · on GitHub

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/PatrickJS/awesome-cursorrules

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 react-graphql-apollo-client-cursorrules-prompt-file

README.md
[![agentmods](https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/react-graphql-apollo-client-cursorrules-prompt-file.svg)](https://agentmods.dev/rules/patrickjs/awesome-cursorrules/react-graphql-apollo-client-cursorrules-prompt-file)
Your own site
<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/react-graphql-apollo-client-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/react-graphql-apollo-client-cursorrules-prompt-file.svg" alt="Measured on agentmods" height="20"></a>
Per session 242 This file is loaded in full into every session.
When invoked 242 The same file — it is already loaded in full.
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.00242 $0.00242
Opus 5 $0.00121 $0.00121
Sonnet 5 $0.00048 $0.00048
Haiku 4.5 $0.00024 $0.00024

Measured 3d ago against content hash 606da4255338, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

react-graphql-apollo-client-cursorrules-prompt-file 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 3d 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.

rules/react-graphql-apollo-client-cursorrules-prompt-file.mdc · 47 lines

What it actually says

// React + GraphQL (Apollo Client) .cursorrules

// Prefer functional components with hooks

const preferFunctionalComponents = true;

// GraphQL and Apollo Client best practices

const graphqlBestPractices = [ "Use Apollo Client for state management and data fetching", "Implement query components for data fetching", "Utilize mutations for data modifications", "Use fragments for reusable query parts", "Implement proper error handling and loading states", ];

// Folder structure

const folderStructure = src/ components/ graphql/ queries/ mutations/ fragments/ hooks/ pages/ utils/;

// Additional instructions

const additionalInstructions = `

  1. Use Apollo Provider at the root of your app
  2. Implement custom hooks for Apollo operations
  3. Use TypeScript for type safety with GraphQL operations
  4. Utilize Apollo Client's caching capabilities
  5. Implement proper error boundaries for GraphQL errors
  6. Use Apollo Client DevTools for debugging
  7. Follow naming conventions for queries, mutations, and fragments `;
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. 3d ago First seen · 47 lines · 242 tokens per session scan A 606da4255338

Subscribe to this mod's changes

react-graphql-apollo-client-cursorrules-prompt-file is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,732 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 242 tokens to every session, about $0.0012 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-09-03.