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 T4wroot/agentic-seo --skill shippinggit clone --depth 1 https://github.com/T4wroot/agentic-seoWrote 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/t4wroot/agentic-seo/shipping)<a href="https://agentmods.dev/skills/t4wroot/agentic-seo/shipping"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/shipping/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/t4wroot/agentic-seo/shipping"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/shipping.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.00082 | $0.02670 |
| Opus 5.5 | $0.00033 | $0.01068 |
| Sonnet 5.5 | $0.00016 | $0.00534 |
| Haiku 4.5 | $0.00008 | $0.00267 |
Grade A, and why
shipping-page-generator 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 1mo 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.
This is a copy
100% identical to shipping-page-generator — 229 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pages: Shipping / Delivery
Guides shipping and delivery information page content for e-commerce, covering domestic and cross-border logistics, regulatory compliance, and AI-era discoverability.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Identify:
- Shipping scope: Domestic only, cross-border, or global — see §Shipping Scope
- Product type: Physical goods (standard), digital/physical bundles, print-on-demand, dropshipping
- Carriers & methods: Standard, express, overnight; carrier names; real-time vs flat-rate
- Regulatory exposure: EU (2026 customs changes, AI Act), cross-border compliance
- AI discoverability: Can delivery terms be parsed by AI shopping agents? — see §AI-Era Readiness
Shipping Scope
| Scope | Key Considerations |
|---|---|
| Domestic Only | Simplest; focus on carrier options, timelines, cutoffs, free-shipping thresholds |
| Regional (e.g., EU-wide) | Harmonized customs within single market; local carrier partnerships; OOH networks |
| Cross-Border / Global | DDP vs DDU; customs duties transparency; multi-carrier tracking normalization; per-market configurability |
AI-Era Readiness — Critical for 2026
The most significant shift in 2025–2026: 58% of consumers have replaced traditional search engines with GenAI tools for product research and price comparison (Capgemini 2026). AI shopping agents compare delivery dates, costs, return terms, and total landed costs before the shopper ever visits your site.
What this means for shipping policies:
- Delivery terms must be machine-readable and structured — an AI agent scraping your site must be able to extract delivery promises, costs, cut-off times, and geographic availability
- If your delivery terms are buried in unstructured paragraphs, AI agents may exclude your brand from consideration entirely
- Standardize delivery options in consistent formats: option name | cost | timeline | cutoff | regions
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.
- 1mo ago First seen · 229 lines · 82 tokens per session scan A c7eb95ef2a75
shipping-page-generator is a skill published in the GitHub repository T4wroot/agentic-seo (15 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 2,670 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to shipping-page-generator, differing in 229 lines, and is treated as a copy.
Other skills, from other repositories
distribution-channels
When the user wants to plan product distribution via marketplaces, app stores, or third-party platforms. Also use when the user mentions "distribution channels," "marketplace listing," "app store listing," "Figma plugin," "Chrome extension marketplace," "AWS Marketplace," "Shopify app," "GPTs store," "app…
category-page-generator
When the user wants to create, optimize, or audit e-commerce category pages or listing pages. Also use when the user mentions "category page," "product category," "faceted navigation," "filter URLs," "e-commerce listing," "category SEO," "category structure," "product filters," or "listing page." For programmatic SEO…
products-page-generator
When the user wants to create, optimize, or audit a product listing or category page. Also use when the user mentions "product page," "product listing," "shop," "e-commerce products," "product catalog," "product grid," "product cards," or "product overview." For category SEO, use category-page-generator.
directory-listing-ads
When the user wants to run paid ads within directories or marketplaces. Also use when the user mentions "Taaft ads," "Shopify App Store ads," "G2 sponsored," "Capterra ads," "directory ads," "marketplace ads," "paid listing," "sponsored listing," or "directory promotion." For organic listings, use directory-submission.
paid-ads-strategy
When the user wants to plan paid ads strategy, allocate ad budget, or choose paid channels. Also use when the user mentions "paid ads," "paid media," "PPC," "SEM," "web ads," "app ads," "TV ads," "CTV," "OOH," "banner ads," "ad network," "ad alliance," "Taaft ads," "Shopify App Store ads," "Google Ads," "Meta Ads,"…
conversion-optimization
When the user wants to improve conversion rates, run A/B tests, optimize funnels, or reduce friction. Also use when the user mentions "CRO," "conversion rate optimization," "A/B test," "split test," "funnel optimization," "checkout optimization," "form optimization," or "conversion funnel." For pricing psychology, use…