FounderOS: Command for Claude Code

.claude/commands/legal-update.md

legal-update is a command for Claude Code from ARCASSystems/FounderOS. It costs 40 tokens per session (1,054 once invoked), scanned A, original, MIT.

A command for refreshing the legal and compliance sources used for a chosen jurisdiction. It checks whether sources have changed and records when they were last checked.

In plain words
What is it for?
Use it for quarterly source reviews or pre-memo checks, including identifying stale sources and updating their check dates.
Why use it?
It reduces the risk of relying on legal references that are out of date, especially before writing a client-facing legal memo.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is ARCASSystems/FounderOS's own configuration. It tells Claude Code how to work on FounderOS itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything FounderOS configures →

Part of the founder-os plugin — 95 skills, 45 commands, 6 hooks shipped together

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/ARCASSystems/FounderOS/main/.claude/commands/legal-update.md
Clone the repo
git clone --depth 1 https://github.com/ARCASSystems/FounderOS

Made for: Claude Code.

Or install founder-os, the plugin that ships this one along with the rest of its 95 skills, 45 commands, 6 hooks.

Wrote 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.

agentmods badge for legal-update

README.md
[![agentmods](https://agentmods.dev/badge/commands/arcassystems/founderos/legal-update.svg)](https://agentmods.dev/commands/arcassystems/founderos/legal-update)
Your own site
<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>
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,054 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 622963a1468a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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.

.claude/commands/legal-update.md · 73 lines

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.

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

  1. Verify install. If core/identity.md does not exist, reply: Founder OS not set up here. Say "set up Founder OS" first. and stop.

  2. Read jurisdiction. Open core/identity.md and find the jurisdiction: field. If missing, reply: No jurisdiction set. Say "set up legal" first. and stop.

  3. 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.

  4. 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".

  5. 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>
  - ...
  1. 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's notes: field for this source AND update the relevant domain file's '## Material Changes Since' block? (yes / no)". If yes, do both edits. Update last_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.yml after a confirmation prompt: "Drop <source-key> permanently? Will not auto-restore. (yes / no)"

Read the full file on GitHub · 73 lines

Changes

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.

  1. 8d ago First seen · 73 lines · 40 tokens per session scan A 622963a1468a

Subscribe to this mod's changes

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.