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 dalroot/agentic-seo --skill refundgit clone --depth 1 https://github.com/dalroot/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/dalroot/agentic-seo/refund)<a href="https://agentmods.dev/skills/dalroot/agentic-seo/refund"><img src="https://agentmods.dev/badge/skills/dalroot/agentic-seo/refund/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/dalroot/agentic-seo/refund"><img src="https://agentmods.dev/badge/skills/dalroot/agentic-seo/refund.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.00080 | $0.02960 |
| Opus 5.5 | $0.00032 | $0.01184 |
| Sonnet 5.5 | $0.00016 | $0.00592 |
| Haiku 4.5 | $0.00008 | $0.00296 |
Grade A, and why
refund-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 today.
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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pages: Refund / Return Policy
Guides refund and return policy page content for SaaS, digital products, e-commerce, and services. Covers jurisdiction-specific requirements including EU withdrawal rights.
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:
- Product category: See §Product Categories — refund logic is fundamentally different for SaaS vs digital downloads vs physical goods vs services
- Jurisdiction: EU (14-day withdrawal right + mandatory withdrawal button), UK (DMCCA subscription rules), US (FTC clear-and-conspicuous), Australia (consumer guarantees), China (2026 platform rules)
- Refund model: Full refund, partial/pro-rata, store credit only, no refund, or conditional
- Payment flow: One-time, subscription/recurring, or tiered pricing
Product Categories
Refund policies differ radically by product type. Identify the category first:
| Category | Default Refund Stance | Key Considerations |
|---|---|---|
| SaaS / Subscription | Pro-rata or conditional | EU withdrawal button required by Jun 2026; trial periods; auto-renewal cancellation; Sky Austria case may reclassify subscriptions as "digital services" with full-period withdrawal rights |
| Digital Downloads | Typically non-refundable | "Once downloaded, all sales final"; exceptions for technical failure or duplicate purchase; must obtain explicit consent to waive EU withdrawal right before download |
| Physical Goods | 30-day return window (standard) | Return shipping costs; restocking fees; original packaging; final-sale categories |
| Courses / Coaching | Conditional | Pre-recorded: non-refundable once accessed; Live: partial refund before start, none after; rescheduling preferred over refunds |
| API / Usage-Based | Prorated or non-refundable | Pay-as-you-go typically non-refundable; subscription components may be prorated |
| Marketplace | Per-vendor or uniform | Who processes refunds; vendor return rates (>8% review, >15% suspend); uniform policy builds trust |
| Free Tools | N/A | No payment = no refund policy needed; state "free, no purchase required" if asked |
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.
- today First seen · 249 lines · 80 tokens per session scan A b9aeeb39fc08
refund-page-generator is a skill published in the GitHub repository dalroot/agentic-seo (25 stars, last pushed 6d ago), licensed MIT. It adds 80 tokens to every session and 2,960 once invoked, about $0.0003 per session on Opus 5.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-10-26.
Other skills, from other repositories
legal-page-generator
When the user wants to create, optimize, or structure legal pages (Privacy, Terms, etc.). Also use when the user mentions "privacy policy," "terms of service," "legal pages," "cookie policy," "terms and conditions," "legal footer," "legal section," "compliance pages," or "legal requirements." For Privacy Policy…
refund-page-generator
When the user wants to create or optimize a refund or return policy page. Also use when the user mentions "refund policy," "return policy," "money-back guarantee," "returns and refunds," "refund page," "return process," "refund terms," "satisfaction guarantee," "cancellation policy," or "withdrawal right." For legal…
privacy-page-generator
When the user wants to create, optimize, or structure Privacy Policy page. Also use when the user mentions "privacy policy," "privacy page," "data protection," "GDPR compliance," "privacy notice," "data privacy," "CCPA," "cookie policy," or "personal data." For legal overview page, use legal-page-generator.
terms-page-generator
When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," "user agreement," "ToS," "legal terms," "service agreement," or "terms page." For legal overview page, use legal-page-generator.
cookie-policy-page-generator
When the user wants to create or optimize a cookie policy page. Also use when the user mentions "cookie policy," "cookies," "cookie consent," "GDPR cookies," "cookie banner," "cookie notice," "tracking cookies," or "cookie settings." For legal overview, use legal-page-generator.
brand-protection
When the user faces brand impersonation, fake websites, phishing sites, or trademark infringement. Also use when the user mentions "fake site," "impersonation," "phishing site," "trademark infringement," "domain squatting," or "brand abuse." For monitoring, use brand-monitoring.