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.
git clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/commands/christopherlouet/claude-base/legal-terms-of-service)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/legal-terms-of-service"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/legal-terms-of-service/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/commands/christopherlouet/claude-base/legal-terms-of-service"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/legal-terms-of-service.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.00000 | $0.00317 |
| Opus 5 | $0.00000 | $0.00159 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
legal-terms-of-service 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 9d 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
TERMS-OF-SERVICE Agent (ToS)
Generates complete and compliant Terms of Service.
Request context
$ARGUMENTS
Objective
Create professional ToS that legally protect the service while remaining clear and understandable for users.
Workflow
- Collect the publisher's legal information
- Define the key terms of the contract
- Describe the service and access conditions
- Define the obligations of the parties (user and publisher)
- Draft the intellectual property clauses
- Define liability limitations and warranties
- Specify termination conditions and their effects
- Add specific clauses depending on the type (SaaS B2B, marketplace, mobile)
- Generate the pre-publication checklist
Expected output
- Complete ToS with all mandatory sections
- Specific clauses tailored to the type of service
- Checklist for legal compliance, content and form
Related agents
| Agent | Usage |
|---|---|
/legal:legal-privacy-policy |
Privacy policy |
/legal:legal-rgpd |
GDPR compliance |
/legal:legal-docs |
Other legal documents |
/legal:legal-payment |
Sales terms and payments |
IMPORTANT: These ToS are a template. Have them validated by a lawyer before publication.
YOU MUST adapt the content to the type of service (B2B, B2C, marketplace, etc.).
YOU MUST include the mandatory legal notices (LCEN).
NEVER copy ToS without adapting them to the specific context of the service.
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.
- 9d ago First seen · 49 lines · 0 tokens per session scan A 37bdf40609bc
legal-terms-of-service is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 317 tokens. 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-03.
Other commands, from other repositories
migrate
Generate and manage database migrations.
context-stats
Display context window usage and token statistics.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
cancel-ralph
Cancel active Ralph Wiggum loop.
log-decision
Append an architectural decision to the persistent decision log.
update-docs
Scan for recently modified files and update corresponding documentation.