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 agentmods add commands/arcassystems/founderos/updategit clone --depth 1 https://github.com/ARCASSystems/FounderOSWhat 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 | $0.00085 | $0.07389 |
| Opus 5 | $0.00043 | $0.03694 |
| Sonnet 5 | $0.00017 | $0.01478 |
| Haiku 4.5 | $0.00009 | $0.00739 |
Grade A, and why
update scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. `curl -fsSL https://raw.githubusercontent.com/ARCASSystems/FounderOS/main/VERSION` (plain fetch first: `base64 -d` is missing on a bare Windows box) How it starts
The opening of the file, as written. The whole thing — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
- core/ (all files - identity, profile, avatar, voice and brand profiles, setup backlog)
- context/ (all files)
- cadence/ (all files)
- brain/ (all files)
- capture/ (all files - the founder's inbox drops)
- brands/ (all files - per-brand voice and positioning)
- network/ (all files)
- clients/ (all files)
- companies/ (all files)
- roles/ (the employee registry - operator-owned statuses, review stamps, custom rows)
- system/ (the quarantine catch-net - this install's failure record)
- any company or project folder setup created at the OS root (Phase 3 execution workspaces - arbitrary names, always the founder's)
- MEMORY.md (and any memory/ directory)
- stack.json (local tool bindings generated by setup)
- os-config.yaml (which modules this install runs, plus the founder's own brand values)
- VERSION does NOT count as User Layer - it is the System Layer marker.
The User Layer is owned by the founder. If you cannot determine whether a file is User Layer or System Layer, REFUSE the update and report the ambiguous path. Do not guess. Do not silently overwrite the founder's data. Better to refuse than corrupt.
The same discipline applies to the three PROTECTED LIVE FILES (root CLAUDE.md, rules/, .claude/settings.json): the update may PROPOSE changes to them and apply on an explicit yes, but never overwrite them wholesale. They carry the founder's personalization and edits.
Founder OS update
Pulls the latest System Layer files from the public repo (ARCASSystems/FounderOS) and applies them to this install. The User Layer (core, context, cadence, brain, capture, brands, network, clients, companies, memory, local stack bindings) stays untouched.
Argument: $ARGUMENTS - optional. One of: check, rollback, or empty.
Layer definitions (memorize before running)
System Layer (safe to update):
.claude/(commands, hooks, agents - but NOTsettings.json, see Protected live files).claude-plugin/(plugin.json, marketplace.json)skills/(shared skill definitions)scripts/(all Python helpers shipped by the OS - the fulltemplates/scripts/set)templates/(structural templates - incoming bootloader and rules changes land here)notion-package/(Notion setup assets)updates/(release packs - additive files, one per release per change group)docs/(user-facing documentation)AGENTS.md(cross-agent instructions)GEMINI.md(cross-agent bridge)README.mdCHANGELOG.md(release history - the Step 10 digest reads it)VERSIONstate/(the OS's own scratch: update backups and manifests, session-change snapshots - never founder content)
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.
- 2d ago First seen · 369 lines · 0 tokens per session scan A 1f777334b195
update is a command published in the GitHub repository ARCASSystems/FounderOS (5 stars, last pushed 18d ago), licensed MIT. It adds 85 tokens to every session and 7,389 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
wiki-query
Ask questions against the wiki. Synthesizes answers from wiki pages with cross-reference citations.
wiki-digest
Generate a daily or weekly digest of wiki changes — new sources, pages, insights, and gaps.
demo-command
Example slash command that wraps the demo-skill. Showcases the command kind.
ingest-l1
L1 analysis loop for the abapwiki knowledge base: for each batch it launches the abap-analyzer sub-agent in parallel, then the adversarial judge abap-deepcheck (separate session), applies only the analyses that pass the fail-closed gate, and commits. Resumes exactly after an interruption. Use this skill to document…
web-search
Search fetched web-source Markdown by regex and pull surrounding context for the best hits. Optionally restrict to one source alias.
docs-refresh
Re-fetch a cached source, ignoring the 7-day cache. Use when upstream content has changed.