Borrowing it
Nothing to install: this file belongs to ARCASSystems/FounderOS. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ARCASSystems/FounderOS/main/.claude/commands/legal-update.mdgit clone --depth 1 https://github.com/ARCASSystems/FounderOSWrote 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/arcassystems/founderos/legal-update)<a href="https://agentmods.dev/commands/arcassystems/founderos/legal-update"><img src="https://agentmods.dev/badge/commands/arcassystems/founderos/legal-update.svg" alt="Measured on agentmods" 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.00040 | $0.01054 |
| Opus 5 | $0.00020 | $0.00527 |
| Sonnet 5 | $0.00008 | $0.00211 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
legal-update 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 8d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Legal & Compliance Update
Quarterly refresh of the loaded jurisdiction's source set. Walks each source, prompts you to web-search it, captures any material changes, and updates last_checked_on: dates so the skill stops flagging the source as stale.
Procedure
-
Verify install. If
core/identity.mddoes not exist, reply:Founder OS not set up here. Say "set up Founder OS" first.and stop. -
Read jurisdiction. Open
core/identity.mdand find thejurisdiction:field. If missing, reply:No jurisdiction set. Say "set up legal" first.and stop. -
Open sources.yml. Read
skills/legal-compliance/references/<jurisdiction>/sources.yml. If missing, reply:No source set loaded for <jurisdiction>. Say "set up legal" to create the scaffold, or "add a legal source" to add sources directly.and stop. -
Identify stale sources. Today's date minus each source's
last_checked_on:. Anything >180 days old is "stale". Anything >90 days old is "warming". Anything ≤90 days is "fresh". -
Show the user the audit:
Source freshness audit for <jurisdiction> as of <today>:
Stale (>6 months - refresh now):
- <source-key>: <name>, last checked <date>, <N> days ago
- ...
Warming (3-6 months - refresh recommended):
- <source-key>: <name>, last checked <date>
- ...
Fresh (<3 months - no action):
- <source-key>: <name>, last checked <date>
- ...
-
Walk each stale source one at a time. Ask: "Refresh
<source-key>()? Options: yes / skip / mark-checked-no-changes / drop-source"- yes: WebFetch the source URL. Look for material changes (new amendments, ministerial decisions, threshold updates, fee changes). Show the user a summary: "Found / did not find material changes since <last_checked_on>." If material changes are found, ask: "Add a one-line note to
sources.yml'snotes:field for this source AND update the relevant domain file's '## Material Changes Since' block? (yes / no)". If yes, do both edits. Updatelast_checked_on:to today's date. - skip: leave as-is, move to next source.
- mark-checked-no-changes: update
last_checked_on:to today's date without web-fetching. Use when the user has already verified the source themselves. - drop-source: the source is no longer authoritative. Remove the entry from
sources.ymlafter a confirmation prompt: "Drop<source-key>permanently? Will not auto-restore. (yes / no)"
- yes: WebFetch the source URL. Look for material changes (new amendments, ministerial decisions, threshold updates, fee changes). Show the user a summary: "Found / did not find material changes since <last_checked_on>." If material changes are found, ask: "Add a one-line note to
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.
- 8d ago First seen · 73 lines · 40 tokens per session scan A 622963a1468a
legal-update is a command published in the GitHub repository ARCASSystems/FounderOS (5 stars, last pushed 24d ago), licensed MIT. It adds 40 tokens to every session and 1,054 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-08-31.
Other commands, from other repositories
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.
compliance-audit
Full regulatory compliance audit for GDPR, HIPAA, SOC2, PCI-DSS, ISO 27001, and other frameworks with gap analysis, remediation planning, and evidence collection.
india-checklist
Interactive non-code compliance checklist — business registration, DPO, GST, CERT-In, grievance officer, and more.
arckit.fr-rgpd
You are helping an enterprise architect generate a French CNIL Compliance Assessment — the French-specific GDPR layer applied by the CNIL (Commission Nationale de l'Informatique et des Libertés). Run this after /arckit:eu-rgpd to add French obligations that go beyond the EU GDPR baseline.
rgpd
Questões de RGPD e violação de dados — referência, playbook e checklist. GDPR and data-breach matters — reference, playbook and checklist.