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 zgbrenner/agentcounsel --skill terms-of-service-reviewgit clone --depth 1 https://github.com/zgbrenner/agentcounselWrote 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/zgbrenner/agentcounsel/terms-of-service-review)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/terms-of-service-review"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/terms-of-service-review/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/zgbrenner/agentcounsel/terms-of-service-review"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/terms-of-service-review.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.00034 | $0.02958 |
| Opus 5 | $0.00017 | $0.01479 |
| Sonnet 5 | $0.00007 | $0.00592 |
| Haiku 4.5 | $0.00003 | $0.00296 |
Grade A, and why
Terms of Service Review 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.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terms of Service Review
Purpose
Produce a structured, attorney-ready review of a terms of service (ToS) or terms of use (ToU) document, for either a consumer (B2C) or business-to-business (B2B) context. This skill assesses key legal provisions, identifies missing or one-sided terms, flags enforceability concerns, and notes inconsistencies with linked policies. It produces draft legal work product for attorney review — not legal advice, and not a determination that any provision is enforceable or compliant.
Use When
- A user asks to "review our terms," "check our ToS," "are our terms okay?" or "what are the risks in this agreement?"
- A company is launching a new product or service and needs its first ToS reviewed before publication.
- An existing ToS is being updated and the changes require legal review.
- A company is evaluating a third party's ToS before agreeing to it (e.g., as a developer accepting a platform's terms).
- Legal counsel needs a structured first-pass triage of a lengthy ToS before conducting a detailed substantive review.
- A launch review (see
launch-review) has flagged the ToS as requiring deeper analysis.
Required Inputs
- The full ToS text: uploaded, pasted, or linked. If linked, the text must be retrieved and reviewed — do not rely on a URL alone.
- Product or service context: what the platform or service does, who operates it, and who the users are.
- B2C or B2B context: whether the terms govern consumer relationships, business relationships, or both.
- Jurisdiction: the governing law and dispute resolution forum as stated in the document, and the primary markets where the service operates. Flag as
[CONFIRM: jurisdiction]if not provided. - Linked policies (if available): the linked or incorporated privacy policy, acceptable use policy, refund policy, or other referenced documents.
If the ToS text is not provided, stop and request it. Do not fabricate terms or assume what the document says.
Do Not Use When
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 · 159 lines · 34 tokens per session scan A 97cde63fa760
Terms of Service Review is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 2,958 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
legal-research
A legal research skill for finding and analysing laws and court cases, including similar cases. It requires access to a reliable legal research database before producing a formal report.
document-fill
A document-filling assistant that uses a supplied template and case files to fill in forms, contracts, or legal documents. It also reports where each filled value came from and which details are missing.
contract-review
A contract-review workflow for agreements governed by Chinese law, United States law, or both. It examines clauses one by one and produces a list of legal-risk questions, with an optional marked-up Word document.
terms-generator
Generates comprehensive terms of service by analyzing a website or application to detect business type, data collection, and user interactions. Use when launching a website, app, or SaaS product that needs terms of service with GDPR/CCPA compliance. Trigger with "/terms-generator" or "create terms of service for my…
redline-sentry
Review NDAs, MSAs, DPAs, SaaS agreements, and other procurement contracts against a configurable risk playbook. Use whenever the user drops a contract file (PDF, DOCX) and asks to redline, review, summarise risk, check clauses, or "what would procurement say". Trigger on phrases like "review this NDA", "redline this…
fedramp
Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document…