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/nextgit 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.00040 | $0.01763 |
| Opus 5 | $0.00020 | $0.00881 |
| Sonnet 5 | $0.00008 | $0.00353 |
| Haiku 4.5 | $0.00004 | $0.00176 |
Grade A, and why
next 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 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.
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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/next
Recommend ONE next action across everything the founder is currently doing. This is the orchestration command. It reads priorities, clients, cadence, and brain, then reasons about what to recommend.
Procedure (in order)
Step 0. Route by operator type
Before ranking, check who this is for. Read the **Role:** line under ## Basics in core/identity.md, and whichever snapshot block the file carries (## Founder Snapshot or ## Role Snapshot), if any. The role is the gate, not the profile variant - the variant field never holds team_of_one.
If the role is founder or team_of_one and a ## Founder Snapshot block exists, OR the role is operator and a ## Role Snapshot block exists, do NOT run the generic ranking below. Run the founder-next-move propose engine instead. It reads the same files, works out where they actually are, and names the single highest-leverage move - toward a paying customer on the founder path, toward the work they own on the operator path - with a three-option close. The engine handles a thin snapshot itself - it proposes a capture move when fields are missing - so route to it whenever the matching block exists, even half-filled. Never send someone who has a snapshot to the generic ranking.
For every other case (no identity file, a student / career-mover install with no snapshot block, or an older install carrying neither block), continue with the ranking in Steps 1 to 5 below.
Step 1. Verify setup
Read context/priorities.md. If the file does not exist or only contains template placeholders, reply:
Priorities not set up. Run
/founder-os:setupand add at least one weekly priority, or editcontext/priorities.mddirectly. I can't recommend a next action without knowing what matters this week.
Stop.
Step 2. Read context
Read these files in this order. Use whatever is present, skip what is missing.
context/priorities.md- this week's must/should/could (REQUIRED)context/clients.md- active deals and prospects (REQUIRED)brain/needs-input.md- any open ask blocking a workflow (skip if file missing)brain/flags.md- OPEN flags only (skip if file missing)context/decisions.md- any item whose re-trigger condition has fired today (skip if file missing)cadence/daily-anchors.md- today's anchors (skip if file missing or stale)cadence/weekly-commitments.md- this week's commitments (skip if file missing or stale)brain/log.md- last 3 entries only (skip if file missing)
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 · 119 lines · 40 tokens per session scan A c28374ce4b43
next is a command published in the GitHub repository ARCASSystems/FounderOS (5 stars, last pushed 18d ago), licensed MIT. It adds 40 tokens to every session and 1,763 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
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.