GenOffice is an open-source office suite for editing Word, Excel, PowerPoint, PDF, and Markdown files with AI-assisted document editing. People use it as an alternative to Microsoft Office on macOS, Windows, and Linux.
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 genspark-ai/genoffice --skill terms-of-servicegit clone --depth 1 https://github.com/genspark-ai/genofficeWrote 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/genspark-ai/genoffice/terms-of-service)<a href="https://agentmods.dev/skills/genspark-ai/genoffice/terms-of-service"><img src="https://agentmods.dev/badge/skills/genspark-ai/genoffice/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/skills/genspark-ai/genoffice/terms-of-service"><img src="https://agentmods.dev/badge/skills/genspark-ai/genoffice/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.00032 | $0.00919 |
| Opus 5.5 | $0.00013 | $0.00368 |
| Sonnet 5.5 | $0.00006 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
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 today.
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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a terms-of-service specialist. The user describes the product's form (app / website / SaaS / mini-program / open-source tool) and its main features; you generate the matching clauses module by module and deliver the terms of service with a companion privacy notice. The output is not legal advice; a lawyer should review it before launch.
Workflow
- Understand the product: list the feature modules as you understand them (accounts, content posting, payments, subscriptions, virtual goods, third-party login, API, community interaction, use by minors and so on) for the user to confirm or add to. Features determine clauses; a missed module is a missing block of rules.
- Collect the essentials in one go: operating entity, user base (individuals / businesses, whether minors are included), pricing model and refund rules, whether there is UGC, whether third-party services are integrated, service regions.
- Build the document as a Word document with the document tools available here, titled along the lines of "[Product Name] Terms of Service".
- Fixed skeleton: acceptance and updates, definitions, account registration and security, service content and changes, user conduct, intellectual property, disclaimers and limitation of liability, termination, governing law and dispute resolution, contact.
- Insert a dedicated chapter per feature module, each covering only rules for that feature: the UGC chapter covers content licence, moderation, removal and appeals; the payments chapter covers price display, payment, invoicing, refunds and how to cancel auto-renewal; the third-party services chapter covers the boundary of responsibility; the minors chapter covers guardian consent and spending limits.
- Write every rule as "the user may / may not + specific behaviour + consequence"; avoid open-ended wording such as "the platform may take any measures it deems necessary".
- The privacy notice is the second part of the same document (a separate Word document if the user asks), structured: information collected (by feature module), purposes, sharing, storage, user rights, minors, updates and contact. Map each category of information to the feature that triggers its collection.
- Entity name, address, contact details and effective date are placeholders ([Operating Entity], [Contact Email], [Effective Date]); governing law and competent court are left blank for the user to fill in.
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.
- today First seen · 40 lines · 32 tokens per session scan A 8f3940ad5c72
terms-of-service is a skill published in the GitHub repository genspark-ai/genoffice (10,539 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 919 once invoked, about $0.0001 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-10-23.
Other skills, from other repositories
cloud-service-agreement
Draft and fill SaaS agreement templates — cloud contract, MSA, order form, software license, pilot agreement, design partner agreement. Includes variants with SLAs and AI terms. Produces signable DOCX from Common Paper standard forms. Use when user says "SaaS agreement," "cloud contract," "MSA," "order form,"…
data-privacy-agreement
Draft and fill data privacy contract and agreement templates — DPA, data processing contract, GDPR, HIPAA BAA, business associate agreement, AI addendum. Produces signable DOCX files from Common Paper standard forms. Use when user says "DPA," "data processing agreement," "HIPAA BAA," "business associate agreement," or…
mqc-chronicle-master
A document-preparation workflow that turns a collection of legal materials into a dated case timeline. It copies facts from the source, records dates, parties, page references, and conflicts, and produces Word, Excel, and a short visual version.
nda
Draft and fill NDA contract templates — mutual NDA, one-way NDA, confidentiality agreement. Produces signable DOCX files from Common Paper and Bonterms standard forms. Use when user says "NDA," "non-disclosure agreement," "confidentiality contract," "confidentiality agreement," "mutual NDA," or "one-way NDA." Includes…
services-agreement
Draft and fill services agreement templates — consulting contract, contractor agreement, SOW, statement of work, professional services agreement. Produces signable DOCX files from Common Paper and Bonterms standard forms. Use when user says "consulting contract," "contractor agreement," "SOW," "statement of work,"…
法律文件脱敏处理
A browser-based and Python tool for removing sensitive details from legal Word documents and restoring them later. It can replace information such as names, dates, prices, bank accounts and case numbers while preserving document formatting.