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 magento-indexing-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/magento-indexing-caching)<a href="https://agentmods.dev/skills/finsilabs/awesome-ecommerce-skills/magento-indexing-caching"><img src="https://agentmods.dev/badge/skills/finsilabs/awesome-ecommerce-skills/magento-indexing-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/magento-indexing-caching"><img src="https://agentmods.dev/badge/skills/finsilabs/awesome-ecommerce-skills/magento-indexing-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.00032 | $0.03117 |
| Opus 5 | $0.00016 | $0.01558 |
| Sonnet 5 | $0.00006 | $0.00623 |
| Haiku 4.5 | $0.00003 | $0.00312 |
Grade A, and why
magento-indexing-caching scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# Download sitemap and curl each URL with a warm-cache header How it starts
The opening of the file, as written. The whole thing — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Magento Indexing and Caching
Overview
Magento's performance architecture relies on two distinct layers: indexers that pre-compute denormalized data (product prices, search indexes, category paths) into flat tables, and the Full-Page Cache (FPC) that stores complete rendered HTML pages. Varnish is the recommended FPC backend for production, replacing Magento's built-in file-based cache. Redis is the recommended backend for application cache, session storage, and the default cache (block HTML, config, layout). Misconfigured or stale indexes are one of the most common causes of incorrect pricing and product visibility issues.
When to Use This Skill
- When products appear with wrong prices or are invisible after catalog updates
- When implementing Varnish for the first time on a Magento production server
- When diagnosing slow category page loads caused by on-the-fly price calculation
- When configuring Redis for Magento's session and block cache storage
- When setting up cache invalidation after catalog or CMS updates via Magento's cache tags
- When managing indexer schedules on large catalogs (> 50,000 products) to prevent full reindex locking
Core Instructions
-
Understand Magento's indexers and their modes
# List all indexers and their status bin/magento indexer:info bin/magento indexer:status # Example output: # catalog_category_product Category Products valid Update on Save # catalog_product_category Product Categories valid Update on Save # catalog_product_price Product Price invalid Update by Schedule # catalogsearch_fulltext Catalog Search valid Update by Schedule # catalogrule_product Catalog Rule Product invalid Update on SaveSet all production indexers to
Update by Schedulemode to prevent checkout blocking:bin/magento indexer:set-mode schedule catalog_category_product bin/magento indexer:set-mode schedule catalog_product_price bin/magento indexer:set-mode schedule catalogsearch_fulltext bin/magento indexer:set-mode schedule catalog_product_flat bin/magento indexer:set-mode schedule catalog_category_flat # Verify modes bin/magento indexer:show-mode
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/custom-module-cache-tag-invalidation/criteria.json 2.5 KB
- evals/custom-module-cache-tag-invalidation/task.md 2.5 KB
- evals/indexer-production-configuration/criteria.json 2.9 KB
- evals/indexer-production-configuration/task.md 1.6 KB
- evals/redis-cache-and-session-configuration/criteria.json 2.9 KB
- evals/redis-cache-and-session-configuration/task.md 1.7 KB
- tile.json 236 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.
- 9d ago First seen · 325 lines · 32 tokens per session scan A efbbfb888a82
magento-indexing-caching is a skill published in the GitHub repository finsilabs/awesome-ecommerce-skills (52 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 3,117 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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 Strategy Advisor
Recommends the right caching layer, TTL strategy, and invalidation approach for any application bottleneck.
ap2-dev-patterns
Apply AP2 cross-cutting development patterns — multi-agent payment architecture, UCP integration, x402 crypto payments, testing with mock providers, and production deployment. Use when architecting agentic payment systems or solving cross-cutting payment concerns.
acp-dev-patterns
Cross-cutting ACP development patterns — idempotency, error handling, 3D Secure flows, request signing, rate limiting, monitoring, and security best practices. Use when designing architecture or solving production concerns.
ap2-cart-mandate
Implement the AP2 Cart Mandate — the human-present VDC that binds user authorization to a specific transaction with merchant-signed product offers and user-signed confirmation. Use when building cart creation, signing, and verification for human-present checkout flows.
ap2-human-not-present-flow
Implement the AP2 human-not-present transaction flow — autonomous agent shopping with Intent Mandate authorization, constraint enforcement, and merchant escalation. Use when building autonomous agent purchasing that works after the user has left.
ap2-human-present-flow
Implement the AP2 human-present transaction flow — the checkout process where the user is actively present to confirm cart details and payment method selection. The primary VDC in this flow is the Cart Mandate. Use when building interactive agentic checkout with user in the loop.