Master Agreement Generator
affaan-m/ECC
Builds DRAFT counterparty agreements from one markdown template and a small JSON spec per party, with clauses picked by the party's role.
A skill your agent uses when reviewing whether a website or web application has a visible Terms of Service link accessible from every page.
Install Terms Of Service
$ npx skills add thedaviddias/Front-End-Checklist --skill terms-of-service -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist terms-of-service --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/terms-of-service .claude/skills/terms-of-service && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "terms-of-service" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/terms-of-service into .claude/skills/terms-of-service/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "terms-of-service", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/terms-of-serviceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill terms-of-service -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist terms-of-service --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/terms-of-service .agents/skills/terms-of-service && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "terms-of-service" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/terms-of-service into .agents/skills/terms-of-service/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "terms-of-service", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill terms-of-service -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist terms-of-service --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/terms-of-service .cursor/skills/terms-of-service && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "terms-of-service" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/terms-of-service into .cursor/skills/terms-of-service/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "terms-of-service", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/terms-of-service--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill terms-of-service -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist terms-of-service --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/terms-of-service .gemini/skills/terms-of-service && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "terms-of-service" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/terms-of-service into .gemini/skills/terms-of-service/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "terms-of-service", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist terms-of-serviceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill terms-of-service -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/terms-of-service .github/skills/terms-of-service && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "terms-of-service" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/terms-of-service into .github/skills/terms-of-service/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "terms-of-service", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill terms-of-service -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist terms-of-service --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/terms-of-service .opencode/skills/terms-of-service && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "terms-of-service" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/terms-of-service into .opencode/skills/terms-of-service/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "terms-of-service", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
terms-of-service- GitHub stars
- 74k
- Token cost
- ~585 tokens
- SKILL.md length
- 296 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reviewing whether a website or web application has a visible Terms of Service link accessible from every page.
- Reviewing whether a website
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Web application has a visible Terms of Service link accessible from every page
What it does
Terms Of Service is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing whether a website or web application has a visible Terms of Service link accessible from every page.
Its SKILL.md is about 590 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
It sits in Legal & Compliance, covering Policy and terms drafting. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Reviewing whether a website
- Web application has a visible Terms of Service link accessible from every page
Example prompts
- “/terms-of-service”
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
frontendchecklist.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Terms Of Service loads about 585 tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 34 tokens; SKILL.md has 296 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 296 words, ~585 tokens.
Download SKILL.mdSave it as
.claude/skills/terms-of-service/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- terms-of-service
- description
- Use when reviewing whether a website or web application has a visible Terms of Service link accessible from every page.
- metadata.category
- security
- metadata.priority
- medium
- metadata.difficulty
- beginner
- metadata.estimatedTime
- 10
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/security/terms-of-service
Link to your terms of service in the footer
Terms of Service protect your business by limiting liability, establishing jurisdiction, setting rules for user conduct, and specifying your rights to user-generated content — but only if users could reasonably discover and read them.
Quick Reference
- Link to Terms of Service from the site footer on every page
- Terms of Service (ToS) are not legally required in most jurisdictions, but they are best practice for any service with user accounts
- Courts have found ToS unenforceable when they were not clearly presented or linked before the user took action
- For enforceable acceptance, require users to check a checkbox 'I agree to the Terms of Service' during signup
- Keep terms up to date — outdated terms that contradict current practices can create legal liability
Check
Check whether the website footer contains a link to a Terms of Service page. Verify the link is present on all pages including interior pages. Check that during user registration there is a checkbox or explicit acceptance step for the terms.
Fix
Add a 'Terms of Service' link to the site footer on every page. For services with user accounts, add an explicit acceptance checkbox during registration that links to the terms. Ensure the terms page has a stable URL.
Explain
Explain what Terms of Service are for, why they need to be discoverable before a user takes action, and the difference between browsewrap (just a link) and clickwrap (explicit acceptance) agreements.
Code Review
Review server config, headers, forms, and integration points related to Link to your terms of service in the footer. Flag exact responses, cookies, or browser behaviors that violate the rule, and verify them against the effective production-like response.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/security/terms-of-service
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/terms-of-service of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Terms Of Service next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Terms Of Service this skillthedaviddias/Front-End-Checklist | 74k | — | ~585 | Automated safety check: Pass | MIT | |
| Master Agreement Generatoraffaan-m/ECC | 277k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Pii Contract Analyzegregmos/PII-Shield | 150 | — | ~8.9k | Automated safety check: Notes | MIT | |
| Privacy Eukimlawtech/korean-privacy-terms | 587 | — | ~968 | Automated safety check: Pass | Apache-2.0 | |
| Agents In The Teamborghei/Claude-Skills | 891 | — | ~4.2k | Automated safety check: Pass | MIT | |
| Terms Of Service Generatorzubair-trabzada/ai-legal-claude | 1.8k | — | ~2.9k | Automated safety check: Pass | None |
Similar skills
Pii Contract Analyze
gregmos/PII-Shield
Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.
Privacy Eu
kimlawtech/korean-privacy-terms
EU 사용자 대상 서비스용 Privacy Notice·Terms of Service·Consent Modal·Cookie Banner 자동 생성.
Agents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
Terms Of Service Generator
zubair-trabzada/ai-legal-claude
Generates complete, GDPR/CCPA-compliant Terms of Service for a website or SaaS product, with plain English summaries for each section
Tos Clause Scanner
zebbern/claude-code-guide
Audit Terms of Service, user agreements, and privacy policies for consumer risks, producing a structured report that flags unfair clauses, data traps, and liability issues.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Related
Categories
Questions about Terms Of Service
What does Terms Of Service do?
A skill your agent uses when reviewing whether a website or web application has a visible Terms of Service link accessible from every page. Terms Of Service is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing whether a website or web application has a visible Terms of Service link accessible from every page.
When should I use Terms Of Service?
Terms Of Service fits situations like: reviewing whether a website; web application has a visible Terms of Service link accessible from every page.
How do I install Terms Of Service in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill terms-of-service -a claude-code`. Or copy the skill folder (skills/terms-of-service in thedaviddias/Front-End-Checklist) into .claude/skills/terms-of-service in your project. Claude Code loads it when a task matches its description.
How do I install Terms Of Service in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill terms-of-service -a codex`. Or copy the skill folder (skills/terms-of-service in thedaviddias/Front-End-Checklist) into .agents/skills/terms-of-service in your project. Codex loads it when a task matches its description.
Can I use Terms Of Service in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill terms-of-service -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/terms-of-service, .gemini/skills/terms-of-service, .github/skills/terms-of-service and .opencode/skills/terms-of-service in your project.
What does Terms Of Service need to run?
SKILL.md names no scripts, command-line tools or credentials: Terms Of Service is instructions for the agent only.
Does Terms Of Service access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Terms Of Service safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Terms Of Service use?
Terms Of Service is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Terms Of Service use?
About 585 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
What are the alternatives to Terms Of Service?
Skills that share tags, products or a category with Terms Of Service: Master Agreement Generator (affaan-m/ECC, 277k stars), Pii Contract Analyze (gregmos/PII-Shield, 150 stars), Privacy Eu (kimlawtech/korean-privacy-terms, 587 stars) and Agents In The Team (borghei/Claude-Skills, 891 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Terms Of Service?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.