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 nexscope-ai/eCommerce-Skills --skill ecommerce-returns-managementgit clone --depth 1 https://github.com/nexscope-ai/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/nexscope-ai/ecommerce-skills/ecommerce-returns-management)<a href="https://agentmods.dev/skills/nexscope-ai/ecommerce-skills/ecommerce-returns-management"><img src="https://agentmods.dev/badge/skills/nexscope-ai/ecommerce-skills/ecommerce-returns-management/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/nexscope-ai/ecommerce-skills/ecommerce-returns-management"><img src="https://agentmods.dev/badge/skills/nexscope-ai/ecommerce-skills/ecommerce-returns-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 21 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00035 | $0.00521 |
| Opus 5 | $0.00017 | $0.00260 |
| Sonnet 5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
ecommerce-returns-management 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 11d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E-Commerce Returns Management 📥
Optimize e-commerce returns process and reduce return rates. Returns policy design, reverse logistics, root cause analysis, and customer retention through better returns experience.
Supported platforms: Amazon, Shopify, WooCommerce, Walmart, TikTok Shop, Etsy, eBay, BigCommerce.
Built by Nexscope — your AI assistant for smarter e-commerce decisions.
Install
npx skills add nexscope-ai/eCommerce-Skills --skill ecommerce-returns-management -g
Usage
My return rate is 22% on Amazon (clothing category). Industry average is 15-20%. Help me analyze why and reduce it.
Capabilities
- Returns rate benchmarking by category
- Return reason analysis and root cause identification
- Returns policy optimization (balancing customer satisfaction vs cost)
- Reverse logistics workflow design
- Return cost calculation (shipping, restocking, loss)
- Product listing improvements to reduce returns (size guides, photos, descriptions)
- Customer retention strategies post-return
How This Skill Works
Step 1: Collect information from the user's message — product, platform, current situation, and goals.
Step 2: Ask one follow-up with all remaining questions using multiple-choice format. Allow shorthand answers (e.g., "1b 2c 3a").
Step 3: Research and analyze using the frameworks and methodology below.
Step 4: Deliver structured, actionable output with specific recommendations, not vague advice.
Output Format
- Start with a summary of findings
- Include specific data points and benchmarks where available
- Provide prioritized action items
- Mark estimates with ⚠️ when based on incomplete data
- End with concrete next steps
Other Skills
More e-commerce skills: nexscope-ai/eCommerce-Skills
Amazon-specific skills: nexscope-ai/Amazon-Skills
Built by Nexscope — your AI assistant for smarter e-commerce decisions.
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.
- 11d ago First seen · 65 lines · 35 tokens per session scan A 2bcd2d6a1279
ecommerce-returns-management is a skill published in the GitHub repository nexscope-ai/eCommerce-Skills (908 stars, last pushed 15d ago), licensed MIT. It adds 35 tokens to every session and 521 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-08-30.
Other skills, from other repositories
ecommerce-seo-auditor
Audit ecommerce websites, product pages, collection pages, and marketplace listings for technical SEO, crawlability, indexability, on-page relevance, content, internal linking, product data, images, and Core Web Vitals. Use when the user asks for an ecommerce SEO audit, store SEO checkup, product-page review…
buyer-intent-writer
Write or rewrite ecommerce product descriptions, bullets, buying-guide sections, and landing-page copy around verified buyer needs, objections, comparisons, and purchase intent. Use when the user asks for buyer-intent copy, product copy, conversion copy, or a clearer product description. Do not use for technical…
competitor-seo-analyzer
Compare observable ecommerce competitor SEO, content, structured-data, trust, and buyer-intent signals. Use when the user asks for competitor SEO analysis, an SEO comparison, content gaps, or a comparison of supplied pages, listings, exports, or search evidence. Do not infer live rankings, traffic, backlinks, or AI…
ecommerce-geo-auditor
Diagnose an ecommerce page or listing for GEO, AI-search, AI-citation, and AI-shopping readiness using inspected page evidence, supplied content, or crawl data. Use when the user asks for a GEO audit, AI visibility readiness check, AI search audit, citation-readiness review, or why a product is hard for AI systems to…
ecommerce-geo-optimizer
Turn verified ecommerce GEO, AI-search, or AI-citation readiness gaps into a prioritized implementation plan covering content, product facts, technical access, structured data, trust, and measurement. Use when the user asks to improve GEO, optimize for AI search, fix a GEO audit, or create an AI visibility readiness…
faq-content-generator
Generate accurate ecommerce FAQs from verified product facts, buyer questions, reviews, policies, and support evidence. Use when the user asks to write product FAQs, store FAQs, buyer questions, support content, or optional matching FAQPage JSON-LD. Do not promise rich results or invent answers.