Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add cogni-work/insight-wave/plugin install cogni-websiteWrote 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/cogni-work/insight-wave/website-legal)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/website-legal"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/website-legal/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/cogni-work/insight-wave/website-legal"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/website-legal.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.00216 | $0.02735 |
| Opus 5.5 | $0.00086 | $0.01094 |
| Sonnet 5.5 | $0.00043 | $0.00547 |
| Haiku 4.5 | $0.00022 | $0.00274 |
Grade A, and why
website-legal 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.
Website Legal
Generate jurisdiction-specific legal pages from reviewable boilerplate templates. The skill never invents legal text — all wording comes from the template bundles in references/jurisdictions/. Claude only fills {{placeholders}} with facts captured from the user.
Disclaimer
The generated pages are templates, not legal advice. Always print the disclaimer in the final summary: "Diese Texte sind Vorlagen. Vor der Veröffentlichung durch eine Anwältin oder einen Anwalt prüfen lassen." Adapt the disclaimer to project language.
Prerequisites
A website-project.json must exist in the working directory. If missing, redirect to website-setup. A website-plan.json is not required — website-legal can run before or after website-plan. If the plan does not yet exist, the skill writes the legal page entries to a queue file (legal-pages.json) that website-plan will pick up.
Workflow
1. Load Project
Read website-project.json. Extract:
language(drives all user-facing prompts and template language; defaultde)company(name, tagline, contact)legal_config(may be missing, partial, or complete)
If legal_config is missing, create an empty object.
2. Determine Jurisdiction
If legal_config.jurisdiction is not set, ask the user via AskUserQuestion:
"In welcher Rechtsordnung wird die Website veröffentlicht?"
Options:
- Deutschland (DE) — TMG §5, DSGVO, Telemediengesetz
- Österreich (AT) — ECG §5, DSG, DSGVO
- Schweiz (CH) — revDSG, freiwillige Anbieterkennzeichnung
- EU (übrige Mitgliedstaaten) — DSGVO, ePrivacy, generischer Legal Notice
Persist the choice to legal_config.jurisdiction.
3. Capture Legal Entity Facts
Read references/legal-config-schema.md to learn the full field set, then check which fields are still missing for the chosen jurisdiction (see the requirement matrix in that file).
Ask only for missing fields. Adapt the questions to project language. Group questions logically — capture the legal entity in one round, then the responsible person, then VAT/registration in a third round so the user is not overwhelmed.
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/jurisdictions/at/cookies.md.tmpl 1.7 KB
- references/jurisdictions/at/datenschutz.md.tmpl 3.1 KB
- references/jurisdictions/at/impressum.md.tmpl 2.6 KB
- references/jurisdictions/ch/cookies.md.tmpl 1.5 KB
- references/jurisdictions/ch/datenschutz.md.tmpl 2.8 KB
- references/jurisdictions/ch/impressum.md.tmpl 2.5 KB
- references/jurisdictions/de/cookies.md.tmpl 2.1 KB
- references/jurisdictions/de/datenschutz.md.tmpl 5.6 KB
- references/jurisdictions/de/impressum.md.tmpl 4.0 KB
- references/jurisdictions/eu/cookies.md.tmpl 1.8 KB
- references/jurisdictions/eu/legal-notice.md.tmpl 2.7 KB
- references/jurisdictions/eu/privacy-policy.md.tmpl 3.3 KB
- references/legal-config-schema.md 7.8 KB
- references/placeholder-schema.md 5.7 KB
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 · 216 tokens per session scan A c67dc6716d16
website-legal is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 216 tokens to every session and 2,735 once invoked, about $0.0009 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-04.
Other skills, from other repositories
fto-triage
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
terms-of-service
Draft terms of service and a companion privacy notice matched to the product's form and feature modules, not legal advice, delivered as a Word document.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.