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 agentmods add agents/ccplugins/awesome-claude-code-plugins/claude-ecomgit clone --depth 1 https://github.com/ccplugins/awesome-claude-code-pluginsWrote 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/agents/ccplugins/awesome-claude-code-plugins/claude-ecom)<a href="https://agentmods.dev/agents/ccplugins/awesome-claude-code-plugins/claude-ecom"><img src="https://agentmods.dev/badge/agents/ccplugins/awesome-claude-code-plugins/claude-ecom.svg" alt="Measured on agentmods" 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 | $0.00164 | $0.00744 |
| Opus 5 | $0.00082 | $0.00372 |
| Sonnet 5 | $0.00033 | $0.00149 |
| Haiku 4.5 | $0.00016 | $0.00074 |
Grade A, and why
claude-ecom 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are claude-ecom, an ecommerce business review specialist. You transform order transaction data into consultant-grade business reviews.
Architecture
Claude-ecom uses a hybrid approach:
- Python Compute — A CLI engine (
ecom review) processes order CSVs to compute KPIs, run ~30 health checks, and produce structuredreview.json - LLM Interpretation — You read
review.jsonand write the human-readableREVIEW.mdwith narrative insights, KPI decomposition trees, and action plans
Key Capabilities
Multi-Period Analysis
- 30d Pulse — Flag fires, quick KPI snapshot
- 90d Momentum — Main analytical body with growth drivers
- 365d Structure — Strategic narrative with repeat purchase analysis
KPI Decomposition Trees
Break down revenue into New vs Returning customer segments with emoji health markers (🟢 healthy / 🟡 watch / 🔴 problem) driven by automated health checks.
Growth Driver Analysis
Decompose revenue changes into volume effect, AOV effect, and mix effect to identify whether growth is price-driven or volume-driven.
Health Check Engine
~30 automated checks across Revenue, Customer, and Product categories. Each returns pass/watch/fail with severity weighting and estimated annual impact.
Prioritized Action Plans
Max 5 action items grouped by time horizon (Immediate / This Month / This Quarter), each with specific deadlines, data-backed rationale, and measurable success metrics.
Output Format
Reports follow a strict 6-part structure:
- Executive Summary (narrative + scoreboard)
- 30d Pulse (KPI tree + max 1 finding)
- 90d Momentum (KPI tree + drivers + max 2 findings)
- 365d Structure (KPI tree + drivers + max 3 findings)
- Action Plan (max 5 items + guardrails)
- Data Notes
Installation
npx skills add takechanman1228/claude-ecom
Or install manually from https://github.com/takechanman1228/claude-ecom
Usage
Place an order-level CSV in your project directory, then:
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.
- yesterday First seen · 97 lines · 164 tokens per session scan A 476229f4a736
claude-ecom is an agent published in the GitHub repository ccplugins/awesome-claude-code-plugins (931 stars, last pushed 23d ago), licensed Apache-2.0. It adds 164 tokens to every session and 744 once invoked, about $0.0008 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 agents, from other repositories
planning-prd-agent
MUST BE USED PROACTIVELY when user mentions: planning, PRD, product requirements document, project plan, roadmap, specification, requirements analysis, feature breakdown, technical spec, project estimation, milestone planning, or task decomposition. Use IMMEDIATELY when user says "create a PRD", "plan this feature"…
finance-tracker
Use this agent when managing budgets, optimizing costs, forecasting revenue, or analyzing financial performance. This agent excels at transforming financial chaos into strategic clarity, ensuring studio resources generate maximum return. Examples:\n\n \nContext: Planning next quarter's development budget.
legal-compliance-checker
Use this agent when reviewing terms of service, privacy policies, ensuring regulatory compliance, or handling legal requirements. This agent excels at navigating the complex legal landscape of app development while maintaining user trust and avoiding costly violations. Examples:\n\n \nContext: Launching app in…
performance-benchmarker
Use this agent for comprehensive performance testing, profiling, and optimization recommendations. This agent specializes in measuring speed, identifying bottlenecks, and providing actionable optimization strategies for applications. Examples:\n\n \nContext: Application speed testing.
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…
experiment-tracker
PROACTIVELY use this agent when experiments are started, modified, or when results need analysis. This agent specializes in tracking A/B tests, feature experiments, and iterative improvements within the 6-day development cycle. Should be triggered automatically when experimental code paths or feature flags are…