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.
git clone --depth 1 https://github.com/Ad-Superpowers/ad-superpowers-pluginWrote 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/commands/ad-superpowers/ad-superpowers-plugin/ecommerce-health-check)<a href="https://agentmods.dev/commands/ad-superpowers/ad-superpowers-plugin/ecommerce-health-check"><img src="https://agentmods.dev/badge/commands/ad-superpowers/ad-superpowers-plugin/ecommerce-health-check/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/commands/ad-superpowers/ad-superpowers-plugin/ecommerce-health-check"><img src="https://agentmods.dev/badge/commands/ad-superpowers/ad-superpowers-plugin/ecommerce-health-check.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.00020 | $0.00559 |
| Opus 5 | $0.00010 | $0.00280 |
| Sonnet 5 | $0.00004 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
ecommerce-health-check 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 10d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E-Commerce Health Check
Perform a comprehensive e-commerce advertising health check across connected platforms.
Step 1: Gather E-Commerce Data
Pull performance data with e-commerce focus:
Meta Ads:
meta_get_insightswith breakdowns by campaign and ad set for ROAS, purchase value, cost per purchasemeta_get_creativesto check product ad creative health
Google Ads:
google_ads_run_gaql— Shopping campaign performance:SELECT campaign.name, metrics.conversions, metrics.conversions_value, metrics.cost_micros, metrics.all_conversions_from_interactions_rate FROM shopping_performance_view WHERE segments.date DURING LAST_30_DAYS- Search campaign ROAS by product/service keywords
GA4:
ga4_run_report— E-commerce funnel metrics:- Sessions → Product views → Add to cart → Begin checkout → Purchase
- Conversion rate per step
- Revenue by traffic source
TikTok (if connected):
tiktok_get_reportfor product ad performance
Step 2: Funnel Analysis
Calculate and present:
| Funnel Stage | Sessions | Rate | Benchmark | Status |
|---|---|---|---|---|
| Product View | ... | ... | ... | ... |
| Add to Cart | ... | ... | 8-12% | ... |
| Begin Checkout | ... | ... | 40-60% of carts | ... |
| Purchase | ... | ... | 2-4% overall | ... |
Step 3: ROAS Analysis
| Platform | Spend | Revenue | ROAS | Target | Status |
|---|---|---|---|---|---|
| Meta (Prospecting) | ... | ... | ... | >2x | ... |
| Meta (Retargeting) | ... | ... | ... | >5x | ... |
| Google Shopping | ... | ... | ... | >3x | ... |
| Google Search | ... | ... | ... | >4x | ... |
Step 4: Identify Issues & Opportunities
Flag:
- Products/categories with negative ROAS
- Funnel drop-off points above benchmark
- Creative fatigue on product ads
- Budget allocation inefficiencies
- Retargeting window gaps
Step 5: Recommendations
Provide prioritized actions:
- Quick wins (implement this week)
- Medium-term (next 2 weeks)
- Strategic (next month)
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.
- 10d ago First seen · 71 lines · 20 tokens per session scan A 438c6d3d58f1
ecommerce-health-check is a command published in the GitHub repository Ad-Superpowers/ad-superpowers-plugin (5 stars, last pushed 12d ago), licensed MIT. It adds 20 tokens to every session and 559 once invoked, about $0.0001 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-31.
Other commands, from other repositories
feed-audit
Audit Merchant Center feed quality — disapprovals, attributes, identifiers, custom labels.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.