nextjs-cache-handler AGENTS.md

Instructions for using a Redis-based cache with self-hosted Next.js 15 and 16 applications. Redis is a separate service that stores data for quick reuse, and Next.js is a framework for building web applications.

In plain words
What is it for?
Use them when configuring Redis caching, cache invalidation, clustered Redis, TLS connections, or multi-instance Next.js deployments outside Vercel.
Why use it?
They explain important differences between soft and hard cache updates and warn about deployment settings that can cause stale content, broken files, or incorrect results across servers.

Instructions file for CodexOpenCode

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.

agentmods
npx agentmods add instructions/leejpsd/nextjs-cache-handler/agents-md
Clone the repo
git clone --depth 1 https://github.com/leejpsd/nextjs-cache-handler

Made for: Codex, OpenCode.

Per session 496 This file is loaded in full into every session.
When invoked 496 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00496 $0.00496
Opus 5 $0.00248 $0.00248
Sonnet 5 $0.00099 $0.00099
Haiku 4.5 $0.00050 $0.00050

Measured yesterday against content hash f19f7f2b812f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

nextjs-cache-handler AGENTS.md 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 yesterday.

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.

AGENTS.md · 34 lines

What it actually says

@leejpsd/nextjs-cache-handler — notes for AI agents

Redis cache handler for self-hosted Next.js 15/16. Ships BOTH interfaces: cacheHandler (ISR, Next 15+16) and cacheHandlers ('use cache', Next >= 16.1.5). Not for Vercel-hosted apps.

Full agent guidance: skills/nextjs-redis-cache/SKILL.md in this package (also installable via npx skills add leejpsd/nextjs-cache-handler). Agent-executable setup: https://raw.githubusercontent.com/leejpsd/nextjs-cache-handler/main/setup-instructions/setup.md

Rules that prevent the most common mistakes

  1. revalidateTag(tag, "max") is SOFT = stale-while-revalidate: instant stale serve + background re-render, cross-instance convergence in ~1-2s. Brief stale content is BY DESIGN — not a bug. updateTag(tag) is HARD = delete + blocking regeneration. Requires version >= 0.3.3.
  2. cacheMaxMemorySize: 0 in next.config is mandatory for multi-instance correctness. Do not remove it.
  3. DEPLOYMENT_VERSION env must exist at RUNTIME (Docker runner stage). Missing → cross-deploy cache bleed / static chunk 404s.
  4. Redis Cluster needs hashTag: true; TLS via rediss:// URLs.
  5. Build-time ECONNREFUSED toward Redis is expected (build-phase gate) — only investigate if the build fails.
  6. Redis outages degrade to a bounded in-memory fallback with automatic reconnect (backoff 1s→30s). Do not wrap cache calls in extra try/catch.
  7. Wiring shape: two CJS wrapper files + require.resolve in next.config — see README "Quick start" or the setup URL above.

Entry points: /incremental (ISR), /cache-components ('use cache'), /client/redis, /client/ioredis (incl. cluster/sentinel), /ops (metric snapshot), /otel (OpenTelemetry emitter). API details: README.md and https://github.com/leejpsd/nextjs-cache-handler/blob/main/docs/api.md

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. yesterday First seen · 34 lines · 496 tokens per session scan A f19f7f2b812f

Subscribe to this mod's changes

nextjs-cache-handler AGENTS.md is an instructions file published in the GitHub repository leejpsd/nextjs-cache-handler (6 stars, last pushed 6d ago), licensed MIT. It adds 496 tokens to every session, about $0.0025 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-08-31.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

buildNext

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,040 tokens

langchain AGENTS.md

Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens