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 ariadoss/superskills --skill termsgit clone --depth 1 https://github.com/ariadoss/superskillsWrote 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/ariadoss/superskills/terms)<a href="https://agentmods.dev/skills/ariadoss/superskills/terms"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/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/ariadoss/superskills/terms"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/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.00056 | $0.00551 |
| Opus 5.5 | $0.00022 | $0.00220 |
| Sonnet 5.5 | $0.00011 | $0.00110 |
| Haiku 4.5 | $0.00006 | $0.00055 |
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 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.
What it actually says
Pages: Terms of Service
Guides Terms of Service page content, structure, and compliance.
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 type: SaaS, e-commerce, content, marketplace
- Jurisdiction: Governing law, dispute resolution
- User types: B2B, B2C, both
- Indexing: Typically noindex for legal pages
Best Practices
Required Sections
| Section | Content |
|---|---|
| Acceptance | How agreement is formed (signup, use) |
| Service description | What you provide |
| User obligations | Acceptable use, account security |
| Intellectual property | Who owns what |
| Payment | If applicable; billing, refunds |
| Liability | Limitations, disclaimers |
| Termination | When and how accounts end |
| Governing law | Jurisdiction, dispute resolution |
| Changes | How you'll notify of updates |
| Contact | How to reach you about terms |
Content Principles
- Clear language: Plain English where possible
- Structure: Headings, table of contents
- Updates: Date; version if needed
- Legal review: Have lawyer review
Placement
- Footer: Link on every page
- Signup: Require acceptance (checkbox)
- Checkout: Link before purchase
SEO
- Noindex: Common for terms
- Canonical: If multiple versions
Output Format
- Outline (sections)
- Key points per section
- Acceptance flow (signup, checkout)
- Disclaimer: Recommend legal review
Related Skills
- legal-page-generator: Terms is a legal page type
- privacy-page-generator: Often linked together
- contact-page-generator: Contact for terms questions
- indexing: noindex for terms
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 Changed · -16 tokens per session e8bd5f650fbd
- 1mo ago First seen · 70 lines · 72 tokens per session scan A 7e6c686f50e2
terms-page-generator is a skill published in the GitHub repository ariadoss/superskills (12 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 551 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
fto-triage
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
terms-of-service
Draft terms of service and a companion privacy notice matched to the product's form and feature modules, not legal advice, delivered as a Word document.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.