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 monitoring-alerting-commercegit 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/monitoring-alerting-commerce)<a href="https://agentmods.dev/skills/finsilabs/awesome-ecommerce-skills/monitoring-alerting-commerce"><img src="https://agentmods.dev/badge/skills/finsilabs/awesome-ecommerce-skills/monitoring-alerting-commerce/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/monitoring-alerting-commerce"><img src="https://agentmods.dev/badge/skills/finsilabs/awesome-ecommerce-skills/monitoring-alerting-commerce.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.00031 | $0.03189 |
| Opus 5 | $0.00015 | $0.01595 |
| Sonnet 5 | $0.00006 | $0.00638 |
| Haiku 4.5 | $0.00003 | $0.00319 |
Grade A, and why
monitoring-alerting-commerce 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 8d 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitoring & Alerting — Commerce
Overview
Generic infrastructure monitoring (CPU, memory, error rate) is insufficient for e-commerce — you need commerce-domain metrics: checkout funnel conversion rates, payment success/failure breakdown by gateway and card type, cart abandonment rates, and inventory out-of-stock events. This skill covers setting up monitoring across different platforms and instrumenting custom storefronts with OpenTelemetry, building dashboards for commerce KPIs, and setting up alerts that fire before revenue impact becomes visible in sales reports.
When to Use This Skill
- When setting up observability for a new headless storefront or commerce service
- When an incident occurred and you had no alerting in place to catch it early
- When you need real-time visibility into checkout performance and payment failures
- When diagnosing a drop in conversion rate that may be caused by a technical issue
- When preparing SLOs (Service Level Objectives) for the checkout flow before a major sale
Core Instructions
Step 1: Determine your platform and what you can monitor
| Platform | Built-In Monitoring | What You Can Add |
|---|---|---|
| Shopify | Shopify admin shows orders, conversion rates, and a performance report with Core Web Vitals | Install Lucky Orange or Microsoft Clarity for session recordings and funnel drop-off; connect Shopify to Google Analytics 4 for detailed checkout funnel tracking |
| WooCommerce | WooCommerce analytics dashboard shows orders and revenue; no performance monitoring built in | Install MonsterInsights (GA4 integration), WooFunnels (checkout funnel tracking), and set up Uptime Robot (free tier: 50 monitors) for availability alerting |
| BigCommerce | BigCommerce Analytics shows orders, conversion rate, and abandoned carts | Connect BigCommerce to GA4 via native integration; use Lucky Orange for heatmaps and session recordings on checkout pages |
| Custom / Headless | Nothing — you build it | Instrument with OpenTelemetry, ship metrics to Grafana Cloud (free tier: 10K series) or Datadog; build checkout funnel dashboards with PromQL; see implementation below |
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/commerce-alert-rules-and-slo-burn-rate-a/criteria.json 3.8 KB
- evals/commerce-alert-rules-and-slo-burn-rate-a/task.md 1.6 KB
- evals/grafana-commerce-dashboard-and-promql/criteria.json 3.2 KB
- evals/grafana-commerce-dashboard-and-promql/task.md 1.7 KB
- evals/opentelemetry-checkout-instrumentation/criteria.json 3.5 KB
- evals/opentelemetry-checkout-instrumentation/task.md 1.5 KB
- tile.json 263 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.
- 8d ago First seen · 296 lines · 31 tokens per session scan A 9392218acda0
monitoring-alerting-commerce is a skill published in the GitHub repository finsilabs/awesome-ecommerce-skills (52 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 3,189 once invoked, about $0.0002 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
monitoring-logging
Application monitoring, logging systems, and alerting.
monitoring-expert
Expert-level monitoring and observability with Prometheus, Grafana, logging, and alerting. Use when the user mentions observability, Prometheus, Grafana, logging, metrics, or alerting, or when the task involves The Three Pillars of Observability, Monitoring Fundamentals, Prometheus Configuration, or Alert Rules.
monitoring
A guide to monitoring systems with Prometheus and Grafana. Prometheus collects time-based measurements called metrics, while PromQL is the query language used to calculate values such as request rates, errors, resource use, and latency.
prom-query
Prometheus Metrics Query & Alert Interpreter — query metrics, interpret timeseries, triage alerts.
k8s-monitoring-alerting
A Kubernetes diagnostic and repair method for Prometheus and Grafana monitoring problems, including alerts that do not trigger. Prometheus collects measurements, while Grafana displays them in dashboards.
monitoring-setup
Set up comprehensive monitoring with Prometheus, Grafana, and alerting. Covers metrics, dashboards, SLOs, and on-call runbooks.