rules--js-cache-function-results

rules--js-cache-function-results is a cursor rule for Cursor from ratnesh-maurya/cursor-claude-personas. It costs 0 tokens per session (460 once invoked), scanned A, original, MIT.

A JavaScript performance rule for storing results of repeated function calls in a module-level Map. A Map is a built-in key-value store, and caching means reusing an earlier result.

In plain words
What is it for?
Use it for repeated render-time calculations such as converting the same project names into slugs.
Why use it?
It avoids recalculating the same result when a function receives the same input many times during rendering.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it for repeated render-time calculations such as converting the same project names into slugs.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/ratnesh-maurya/cursor-claude-personas/rules-js-cache-function-results
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/ratnesh-maurya/cursor-claude-personas

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 rules--js-cache-function-results

README.md
[![agentmods](https://agentmods.dev/badge/rules/ratnesh-maurya/cursor-claude-personas/rules-js-cache-function-results/github.svg)](https://agentmods.dev/rules/ratnesh-maurya/cursor-claude-personas/rules-js-cache-function-results)
Your own site
<a href="https://agentmods.dev/rules/ratnesh-maurya/cursor-claude-personas/rules-js-cache-function-results"><img src="https://agentmods.dev/badge/rules/ratnesh-maurya/cursor-claude-personas/rules-js-cache-function-results/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 rules--js-cache-function-results

Your own site · 80×15
<a href="https://agentmods.dev/rules/ratnesh-maurya/cursor-claude-personas/rules-js-cache-function-results"><img src="https://agentmods.dev/badge/rules/ratnesh-maurya/cursor-claude-personas/rules-js-cache-function-results.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 460 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.00460
Opus 5 $0.00000 $0.00230
Sonnet 5 $0.00000 $0.00092
Haiku 4.5 $0.00000 $0.00046

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

Security

Grade A, and why

rules--js-cache-function-results 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.

3d-frontend-developer/.cursor/rules/rules--js-cache-function-results.mdc · 81 lines

What it actually says

Cache Repeated Function Calls

Use a module-level Map to cache function results when the same function is called repeatedly with the same inputs during render.

Incorrect (redundant computation):

function ProjectList({ projects }: { projects: Project[] }) {
  return (
    <div>
      {projects.map(project => {
        // slugify() called 100+ times for same project names
        const slug = slugify(project.name)
        
        return <ProjectCard key={project.id} slug={slug} />
      })}
    </div>
  )
}

Correct (cached results):

// Module-level cache
const slugifyCache = new Map<string, string>()

function cachedSlugify(text: string): string {
  if (slugifyCache.has(text)) {
    return slugifyCache.get(text)!
  }
  const result = slugify(text)
  slugifyCache.set(text, result)
  return result
}

function ProjectList({ projects }: { projects: Project[] }) {
  return (
    <div>
      {projects.map(project => {
        // Computed only once per unique project name
        const slug = cachedSlugify(project.name)
        
        return <ProjectCard key={project.id} slug={slug} />
      })}
    </div>
  )
}

Simpler pattern for single-value functions:

let isLoggedInCache: boolean | null = null

function isLoggedIn(): boolean {
  if (isLoggedInCache !== null) {
    return isLoggedInCache
  }
  
  isLoggedInCache = document.cookie.includes('auth=')
  return isLoggedInCache
}

// Clear cache when auth changes
function onAuthChange() {
  isLoggedInCache = null
}

Use a Map (not a hook) so it works everywhere: utilities, event handlers, not just React components.

Reference: How we made the Vercel Dashboard twice as fast

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 · 81 lines · 0 tokens per session scan A 3daaa11d24f4

Subscribe to this mod's changes

rules--js-cache-function-results is a cursor rule published in the GitHub repository ratnesh-maurya/cursor-claude-personas (8 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 460 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.

Related

Other cursor rules, from other repositories

graphql-typescript-integration

A TypeScript rule for GraphQL operations that uses the API schema and queries to generate types. It helps type-check data and variables from the GraphQL server through to React components.

holtwood/awesome-cursorrules-zh · 0 tokens

graphql-apollo-client-usage

A usage guide for fetching, changing, and subscribing to GraphQL data with Apollo Client in React. It covers loading and error states, cache updates, refetching, and reusable GraphQL fragments.

holtwood/awesome-cursorrules-zh · 0 tokens

chakra-ui---component-composition

A React component-structure rule for composing Chakra UI components into reusable interfaces. It favors small custom components built from layout and interface pieces such as Box, Flex, and Stack.

holtwood/awesome-cursorrules-zh · 0 tokens

chakra-ui-best-practices

A set of rules for building React interfaces with Chakra UI, a component library for styled and accessible user interfaces. It covers themes, responsive layouts, accessibility, performance, and reusable components.

holtwood/awesome-cursorrules-zh · 0 tokens

react-general-preferences

A set of React preferences that favors function components with Hooks, which let functions use state and other React features.

holtwood/awesome-cursorrules-zh · 0 tokens

react-functional-components-preference

A React style rule that prefers function components with Hooks such as useState and useEffect over class components. Hooks are React functions for managing state and other component behavior.

holtwood/awesome-cursorrules-zh · 0 tokens