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 termsgit 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/terms)<a href="https://agentmods.dev/skills/dalroot/agentic-seo/terms"><img src="https://agentmods.dev/badge/skills/dalroot/agentic-seo/terms/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/terms"><img src="https://agentmods.dev/badge/skills/dalroot/agentic-seo/terms.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.00072 | $0.02932 |
| Opus 5.5 | $0.00029 | $0.01173 |
| Sonnet 5.5 | $0.00014 | $0.00586 |
| Haiku 4.5 | $0.00007 | $0.00293 |
Grade A, and why
terms-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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pages: Terms of Service
Guides Terms of Service page content, structure, compliance, and AI-specific clauses.
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: Free anonymous, free with account, freemium, subscription SaaS, enterprise/B2B, API/developer, marketplace, e-commerce, content/media, mobile app, AI agent/MCP — see legal-page-generator §Product Categories
- Jurisdiction: Governing law, dispute resolution, whether dual-jurisdiction fallback is needed — see legal-page-generator §Jurisdiction Decision Framework
- AI involvement: Whether AI models generate output, and whether third-party model terms apply — see §AI Clauses
- User types: B2B, B2C, or both
- Indexing: Typically index (see legal-page-generator §Indexing Strategy)
Required Sections (18-Section Framework)
1. Agreement
- "By accessing or using [domain], you agree to be bound by these Terms"
- "If you do not agree, please do not use the service"
- Reference to other incorporated documents (Privacy Policy, AUP, Community Guidelines)
2. The Service
- What the product does in one paragraph
- Fair-use limits: If applicable, state daily/monthly quotas with rationale ("to keep the service fair and available for all users")
- Whether the service is free or paid
3. Eligibility
- Minimum age: 13 (US/COPPA) or 16 (EEA/GDPR)
- Statement: "By using [Product], you confirm that you meet this age requirement"
- Additional restrictions if applicable (e.g., not available in certain countries)
4. No Accounts (If Applicable)
For products without user accounts:
- "No account or sign-up is required"
- User is solely responsible for: content submitted, output generated, compliance with these Terms each session
- User bears the risk of browser/local data loss
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 · 267 lines · 72 tokens per session scan A e7e3aab8499f
terms-page-generator is a skill published in the GitHub repository dalroot/agentic-seo (25 stars, last pushed 6d ago), licensed MIT. It adds 72 tokens to every session and 2,932 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.