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.
npx skills add finsilabs/awesome-ecommerce-skills --skill ecommerce-cachinggit clone --depth 1 https://github.com/finsilabs/awesome-ecommerce-skillsWrote 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.
[](https://agentmods.dev/skills/finsilabs/awesome-ecommerce-skills/ecommerce-caching)<a href="https://agentmods.dev/skills/finsilabs/awesome-ecommerce-skills/ecommerce-caching"><img src="https://agentmods.dev/badge/skills/finsilabs/awesome-ecommerce-skills/ecommerce-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.
<a href="https://agentmods.dev/skills/finsilabs/awesome-ecommerce-skills/ecommerce-caching"><img src="https://agentmods.dev/badge/skills/finsilabs/awesome-ecommerce-skills/ecommerce-caching.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00028 | $0.02697 |
| Opus 5 | $0.00014 | $0.01349 |
| Sonnet 5 | $0.00006 | $0.00539 |
| Haiku 4.5 | $0.00003 | $0.00270 |
Grade A, and why
ecommerce-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.
How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E-commerce Caching
Overview
Implement multi-layer caching for e-commerce applications covering CDN edge caching, application-level caching (Redis), and full-page caching with cart-aware invalidation. This skill addresses the unique challenges of caching commerce pages — personalized content (cart count, logged-in state), frequently changing inventory and prices, and the need for instant cache purging when products or prices change.
When to Use This Skill
- When product and collection pages are slow due to database queries and API calls
- When implementing a CDN or edge caching strategy for a storefront
- When adding Redis caching for product data, inventory, and session management
- When building cache invalidation logic that reacts to product, price, or inventory changes
- When optimizing time-to-first-byte (TTFB) for high-traffic sale events
Core Instructions
Step 1: Determine your platform and what you can control
| Platform | What's Managed For You | What You Control |
|---|---|---|
| Shopify | CDN, full-page caching, server infrastructure | Liquid template efficiency, image optimization, app performance, HTTP cache headers on custom routes |
| WooCommerce | Nothing (you own the server) | Everything: page cache, object cache, CDN, database queries |
| BigCommerce | CDN, full-page caching, server infrastructure | Theme performance, image optimization, app overhead |
| Custom / Headless | Nothing (you own the server) | Everything: CDN configuration, Redis, Varnish, application cache, invalidation |
Step 2: Platform-specific caching configuration
Shopify
Shopify handles CDN and full-page caching automatically. Your optimization levers are:
Theme performance (Liquid):
- Reduce the number of Liquid
{% render %}calls in your product and collection templates — each render tag adds rendering time - In Online Store → Themes → Edit code, avoid loops that query the catalog repeatedly; use
{% liquid %}blocks for conditional logic - Enable Shopify's Lazy loading for product images in Theme settings — this prevents below-fold images from blocking page load
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/cache-control-headers-and-cdn-surrogate-/criteria.json 3.0 KB
- evals/cache-control-headers-and-cdn-surrogate-/task.md 1.9 KB
- evals/event-driven-cache-invalidation-and-pers/criteria.json 3.5 KB
- evals/event-driven-cache-invalidation-and-pers/task.md 2.6 KB
- evals/redis-application-caching-with-ioredis/criteria.json 2.7 KB
- evals/redis-application-caching-with-ioredis/task.md 2.3 KB
- tile.json 241 B
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.
- 7d ago First seen · 246 lines · 28 tokens per session scan A 476755c447ba
ecommerce-caching is a skill published in the GitHub repository finsilabs/awesome-ecommerce-skills (52 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 2,697 once invoked, about $0.0001 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.
Other skills, from other repositories
caching-strategies
Design multi-tier caching architectures for web applications — cache-aside vs write-through vs write-behind, TTL design, cache invalidation, Redis patterns, CDN configuration, browser caching, and stampede prevention. Use when choosing a caching pattern, designing cache invalidation strategies, implementing Redis…
Caching Strategy Advisor
Recommends the right caching layer, TTL strategy, and invalidation approach for any application bottleneck.
cache-strategy-invalidation-expert
Redis caching patterns, cache-aside, write-through, TTL strategies, and invalidation. Activate on: caching, Redis, cache invalidation, cache-aside, write-through, TTL, CDN cache, stale-while-revalidate. NOT for: CDN/reverse proxy setup (use api-gateway-reverse-proxy-expert), database query optimization (use…
caching
Caching strategies — invalidation, TTL guidelines, cache keys, cache layers, and when not to cache. Use when implementing or reviewing caching logic.
caching-strategies
When improving read performance and reducing database load.
redis-state-management
Comprehensive guide for Redis state management including caching strategies, session management, pub/sub patterns, distributed locks, and data structures.