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 skills/arcassystems/founderos/backupnpx skills add ARCASSystems/FounderOS --skill backupgit 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.00122 | $0.01093 |
| Opus 5 | $0.00061 | $0.00547 |
| Sonnet 5 | $0.00024 | $0.00219 |
| Haiku 4.5 | $0.00012 | $0.00109 |
Grade A, and why
backup 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 3d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backup
Runs on: local-exec - runs a local script; on a cloud surface I read the results, I do not run it.
Keep an offsite copy of the founder's OS, to a destination they choose. On command only. Opt-in. Local version control (save, history, restore) already works fully without any of this; backup is the next level.
Pre-flight
- If
core/identity.mddoes not exist, stop with:Founder OS not set up here. Run /founder-os:setup first. - Make clear up front: nothing here is required. Their files and full version history live on their machine already. This adds an offsite copy.
Step 1: pick a destination
Offer these, with the honest trade-off, and let the founder choose. Do not force one.
- GitHub (recommended for long-term durability). A private repo they own. Best for keeping full version history offsite and restoring on a new machine. Needs a free GitHub account and the
ghCLI. - OneDrive, Dropbox, or iCloud. Simplest if they already use one. The folder syncs as files; version history rides along inside the
.gitfolder. - Notion. A reference mirror only, not a live restore target. Useful if Notion is their home base, but it does not preserve git history. Be honest about that limit.
- Stay local. A valid choice. Their work is already saved and undoable locally. Offer to revisit backup later.
Step 2: wire the chosen destination
GitHub
Do NOT re-implement gh auth or repo creation here. Use the github-ops skill (read skills/github-ops/SKILL.md).
- Check
gh auth status. If not authenticated, give the founder the exact step (gh auth login) and stop until done. Do not pretend it is connected. - Create a PRIVATE repo they own:
gh repo create <name> --private --source . --remote origin(confirm the name with them first). - Push:
git push -u origin <current-branch>. Only on the founder's explicit yes. Never force push. - Confirm the push landed (
gh repo view --webor report the repo URL). Do not claim it pushed untilgit pushreturned success.
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.
- 3d ago First seen · 65 lines · 122 tokens per session scan A 7568a1f8b557
backup is a skill published in the GitHub repository ARCASSystems/FounderOS (5 stars, last pushed 19d ago), licensed MIT. It adds 122 tokens to every session and 1,093 once invoked, about $0.0006 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 skills, from other repositories
wiki-ingest
Compile a raw source (document, URL content, meeting notes, research output) into a wikikit agent wiki — merge-don't-overwrite, log contradictions, maintain cross-references, then lint. Use whenever the user says "add this to the wiki", "ingest this", or drops new source material for a wiki maintained with…
markstream-react
Integrate the beta markstream-react package into a React 18+ or Next app. Use when Codex needs to add the React renderer, choose the root, next, or server entrypoint, import CSS correctly, choose between content and nodes, keep client boundaries safe, add renderer-local streamingComponents or htmlComponents, use…
nba
Read the live cycle state and return the single highest-leverage next best action, not a menu. Use when a project is between phases, the author asks what to do next, too many valid threads are open, or the work needs re-entry into frame, build, drive, re0-memo, hate, re0-work, or ship.
review-validation
Validate review findings from specialist agents by reading the actual repo file content and checking each finding for accuracy, applicability, and false positives.
markdown-exporter
Convert Markdown text to DOCX, PPTX, XLSX, PDF, PNG, SVG, HTML, IPYNB, MD, CSV, JSON, JSONL, XML files, and extract code blocks in Markdown to Python, Bash,JS and etc files.
alive:save
The human wants to checkpoint. Or: the stash has grown heavy — 5+ items, 30+ minutes, a natural pause in the work. The squirrel doesn't decide when to save. It surfaces the need and lets the human pull the trigger. Runs the full save protocol: confirms stash, writes log, updates state, generates projections…