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/agents/christopherlouet/claude-base/legal-terms-of-service)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/legal-terms-of-service"><img src="https://agentmods.dev/badge/agents/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/agents/christopherlouet/claude-base/legal-terms-of-service"><img src="https://agentmods.dev/badge/agents/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.00027 | $0.00413 |
| Opus 5 | $0.00014 | $0.00206 |
| Sonnet 5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
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 12d 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
LEGAL-TERMS-OF-SERVICE Agent
Creation of compliant Terms of Service.
Mandatory articles
- Definitions: Service, User, Account, Content, Publisher
- Purpose and acceptance: terms of use, implicit acceptance
- Access to the service: conditions (age of majority, legal capacity), account creation
- Use: authorized and prohibited uses
- Intellectual property: publisher rights, user license, user content
- Responsibilities: publisher (due diligence, security) and user (use, content)
- Subscriptions: pricing, payment, cancellation, refund (if applicable)
- Suspension/Termination: by user and by publisher
- Modifications: notification of substantial changes
- Applicable law and disputes: French law, competent court
- Contact
Workflow
- Analyze the service: type (SaaS, marketplace), B2C/B2B, features
- Generate each article tailored to the service
- Add specific B2B clauses if necessary (liability limitation, confidentiality)
- Integrate GDPR references
Expected output
Complete ToS with:
- All mandatory articles
- Tailored to the type of service
- B2C and/or B2B clauses
- Integrated GDPR compliance
Guidelines
- IMPORTANT: Tailor the ToS to the actual service, not a generic copy-paste
- NEVER forget the applicable law clause
- YOU MUST mention the privacy policy
- IMPORTANT: Clear and understandable clauses (avoid excessive legal jargon)
Think hard about protecting both parties.
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.
- 12d ago First seen · 50 lines · 27 tokens per session scan A 310379a61c20
legal-terms-of-service is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 413 once invoked, about $0.0001 per session on Opus 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-08-31.
Other agents, from other repositories
compliance-engineer
SOC2, HIPAA, GDPR, PCI-DSS compliance implementation specialist. Use when implementing audit logging, data encryption, access controls, privacy by design, or preparing for compliance audits. Trigger phrases: SOC2, HIPAA, GDPR, PCI, compliance, audit log, data privacy, encryption, access control, DSAR, consent.
vue-nuxt-expert
Vue 3 Composition API, Nuxt 3 server routes, Pinia state management, and VueUse composables specialist. Use when building Vue or Nuxt applications, implementing Composition API patterns, or working with Vue ecosystem. Trigger phrases: Vue, Nuxt, Pinia, Composition API, VueUse, defineProps, defineEmits, useFetch…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
api-designer
Designs REST and GraphQL APIs following best practices. Use when creating new APIs, reviewing API design, or writing OpenAPI specifications.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.