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 ThomasMoreAI/legal-skills-open --skill eulagit clone --depth 1 https://github.com/ThomasMoreAI/legal-skills-openWrote 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/thomasmoreai/legal-skills-open/eula)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/eula"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/eula/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/thomasmoreai/legal-skills-open/eula"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/eula.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.00079 | $0.02535 |
| Opus 5.5 | $0.00032 | $0.01014 |
| Sonnet 5.5 | $0.00016 | $0.00507 |
| Haiku 4.5 | $0.00008 | $0.00253 |
Grade A, and why
eula 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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
End-User License Agreement (EULA)
Drafts an enforceable EULA protecting licensor IP, limiting liability, and satisfying consumer protection standards across jurisdictions.
Intake Checklist
Gather before drafting:
- Software — product name, version, deployment model (desktop / mobile / SaaS / cloud / embedded)
- License model — perpetual, subscription, usage-based, freemium, or trial
- User population — B2C, B2B, or mixed; users under 13 (COPPA trigger)
- Geography — US-only, EU, or global (drives GDPR, CCPA applicability)
- Data collected — personal data categories; PHI (HIPAA), financial (GLBA), student (FERPA), payment (PCI-DSS)
- Third-party components — open-source (copyleft vs. permissive) or proprietary
- App store — Apple App Store, Google Play, or direct distribution
- Risk posture — arbitration/class-action waiver? IP indemnification? Benchmark restrictions?
Drafting Workflow
1. Header & Acceptance
- Title: "END-USER LICENSE AGREEMENT" prominently displayed
- Specify triggering act: install / account creation / first use
- Click-wrap required: scrollable full text, accept button active only after scroll opportunity (ProCD v. Zeidenberg; avoid browse-wrap per Specht v. Netscape)
- Mobile: present in app-store listing + first launch; must not contradict platform terms
- Version date + 30-day advance notice for material amendments; affirmative re-acceptance for paid-tier changes reducing rights
2. Definitions
| Term | Scope |
|---|---|
| Software | Product name, version, included modules |
| Updates | Bug fixes / security patches (included) |
| Upgrades | Major versions (may require separate fee) |
| Authorized Users | Named / concurrent / site license scope |
| Documentation | Manuals, API docs, specs |
| Confidential Information | Source code, algorithms, benchmarks, designated materials |
3. License Grant
- Non-exclusive, non-transferable, revocable for breach, [perpetual / subscription-term]
- Specify device count or concurrent user cap
- Permitted use: internal business / personal; per Documentation
- One archival backup copy; proprietary notices intact
- SaaS: frame as access right, not installation right
- Trial: evaluation-only, non-production, time-limited with end date; auto-terminates at expiry
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 · 191 lines · 79 tokens per session scan A 77cd6dfe19b5
eula is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (95 stars, last pushed 15d ago), licensed Apache-2.0. It adds 79 tokens to every session and 2,535 once invoked, about $0.0003 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-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…