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 public-status-pagegit 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/public-status-page)<a href="https://agentmods.dev/skills/nexscope-ai/ecommerce-skills/public-status-page"><img src="https://agentmods.dev/badge/skills/nexscope-ai/ecommerce-skills/public-status-page/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/public-status-page"><img src="https://agentmods.dev/badge/skills/nexscope-ai/ecommerce-skills/public-status-page.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.00374 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
public-status-page 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 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.
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.
What it actually says
Public Status Page
AI-powered public status page design skill for e-commerce businesses. Creates status page architecture, incident communication templates, subscriber notification systems, and uptime reporting frameworks.
Capabilities
- Generates actionable monitoring & alerts frameworks based on your specific business context
- Works across major e-commerce platforms (Amazon, Shopify, Walmart, WooCommerce, Etsy, TikTok Shop)
- Provides data-driven recommendations with industry benchmarks
- Outputs ready-to-implement plans, not just generic advice
Install
clawhub install public-status-page
Usage
Input: Services/systems to monitor, audience (customers/partners), SLA targets
Output: Status page architecture, incident template library, notification subscription design, uptime reporting framework
Example Prompt
"I run a [your business type] on [platform]. Help me set up public status page for my business. Here's my current situation: [describe context]."
Limitations
- Requires your specific business data for accurate recommendations
- Market benchmarks are based on US/EU data — adjust for other regions
- Recommendations should be validated against your platform's current policies
- Does not replace dedicated monitoring SaaS tools — designs the strategy and framework
Built by Nexscope AI — AI-powered e-commerce intelligence.
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 · 57 lines · 0 tokens per session scan A f8c73939cf99
public-status-page is a skill published in the GitHub repository nexscope-ai/eCommerce-Skills (914 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 374 tokens. 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
infrastructure-as-code
Define, deploy, and manage cloud infrastructure as code using tools like Terraform, Pulumi, CloudFormation, and CDK, ensuring consistency, repeatability, and version control. Use when the user requests infrastructure as code or provides relevant inputs for this workflow.
cloud-monitoring
Monitor cloud infrastructure and applications using metrics, logs, and traces to provide real-time observability into performance, health, and reliability. Use when the user requests cloud monitoring or provides relevant inputs for this workflow.
model-deployment
Deploy trained machine learning models as production-ready services using REST APIs, containers, serverless functions, and orchestration platforms. Use when the user requests model deployment or provides relevant inputs for this workflow.
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…