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-docs)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/legal-docs"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/legal-docs/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-docs"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/legal-docs.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.00360 |
| Opus 5.5 | $0.00000 | $0.00144 |
| Sonnet 5.5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
legal-docs 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
LEGAL Agent
Generation of legal documents (Terms of Service, Sales Terms, Legal Notice, Privacy Policy).
Request context
$ARGUMENTS
Objective
Generate the mandatory legal documents adapted to the type of service, with the company information and the specifics of the activity.
Workflow
- Collect information about the company (legal name, SIRET, RCS, address, host)
- Identify the type of service (SaaS, e-commerce, marketplace, content) and the business model
- Determine the necessary documents (legal notice, Terms of Service, Sales Terms, privacy policy, cookies)
- Generate each document with the appropriate standard structure
- Verify the compliance checklist (accessible documents, checkbox, visible date)
- Identify the specific points to validate with a lawyer
Expected output
- Legal notice with all mandatory information
- Terms of Service if user account
- Sales Terms if sale of products/services
- Privacy policy GDPR-compliant
- Checklist for going live
Related agents
| Agent | Usage |
|---|---|
/legal:legal-rgpd |
GDPR audit and compliance |
/legal:legal-privacy-policy |
Detailed privacy policy |
/legal:legal-terms-of-service |
Detailed Terms of Service |
/legal:legal-payment |
Legal aspects of payments |
IMPORTANT: These documents are templates. They must be validated by a legal professional.
YOU MUST fill in all mandatory legal information (SIRET, RCS, etc.).
NEVER copy-paste Terms of Service / Sales Terms from another site — they must reflect the actual activity.
Think hard about the specifics of the activity before generating the documents.
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 First seen · 48 lines · 0 tokens per session scan A 4ba24f60bc9d
legal-docs is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 360 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
context-stats
Display context window usage and token statistics.
migrate
Generate and manage database migrations.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
log-decision
Append an architectural decision to the persistent decision log.
update-docs
Scan recently modified files and update the matching documentation.
backup-config
Backup Claude Code configuration files.