add-caching

A set of application caching changes for storing reusable files and responses so they do not need to be created or downloaded every time. It covers browser, CDN, server-generated, and offline caching.

In plain words
What is it for?
Use it to cache static assets and API responses, regenerate pages periodically, support offline access, and define deployment cache rules.
Why use it?
It reduces repeated work and can make pages and API responses load faster. It also addresses stale data, cache versions, and clearing caches after deployments.

Command

Part of the larouex-fullstack-builder plugin — 46 commands, 12 agents shipped together

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 commands/ashikparvez89/larouex-fullstack-plugin/add-caching
Clone the repo
git clone --depth 1 https://github.com/Ashikparvez89/larouex-fullstack-plugin

Or install larouex-fullstack-builder, the plugin that ships this one along with the rest of its 46 commands, 12 agents.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 106 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00000 $0.00106
Opus 5 $0.00000 $0.00053
Sonnet 5 $0.00000 $0.00021
Haiku 4.5 $0.00000 $0.00011

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

Security

Grade A, and why

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

Origin

This is a copy

100% identical to add-caching — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commands/add-caching.md · 2 lines

What it actually says

Implement comprehensive caching strategy across the application. Configure CDN caching headers in staticwebapp.config.json or Railway configuration. Set cache-control headers for static assets (immutable for hashed files). Implement static generation with revalidation using Next.js ISR. Add client-side caching with SWR or React Query for API responses. Configure stale-while-revalidate patterns. Implement service worker for offline support and asset caching. Add cache versioning strategy. Document cache invalidation procedures for deployments. Test caching behavior in production. Measure performance improvements with faster load times.

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 · 2 lines · 0 tokens per session scan A e988c0883564

Subscribe to this mod's changes

add-caching is a command published in the GitHub repository Ashikparvez89/larouex-fullstack-plugin (3 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 106 tokens. A static security scan graded it A with 0 findings. It is 100% identical to add-caching, differing in 0 lines, and is treated as a copy.