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/rantgit 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.00051 | $0.00914 |
| Opus 5 | $0.00026 | $0.00457 |
| Sonnet 5 | $0.00010 | $0.00183 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
rant 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rant
The user just dropped a rant. Voice-to-text, long, tangential, conversational. The volume is the thinking.
Capture first, qualify second. The previous flow asked a qualifying question before writing - if the user walked away or sent an unrelated message, the rant was lost. That cost is unacceptable. The new flow writes the rant to disk immediately, then offers to route it.
Procedure (in order)
Step 1: Capture immediately
-
Read the user's rant text (whatever followed
/rantor the natural-language trigger like "I want to rant" / "let me dump something"). -
Determine today's date in the user's timezone. Look up timezone from
core/identity.md. If not set, default to local system time. -
Determine the rants file path:
brain/rants/<YYYY-MM-DD>.md. -
If the file does not exist, create it with this header:
# Rants - <YYYY-MM-DD> -
Private-tag filter (mandatory before any write). Scan the source text for
<private>...</private>blocks (case-insensitive). Remove every matched block (including the tags) from the text before writing. If the entire input is wrapped in<private>, write nothing and report "skipped - content was tagged private." -
Prepend a new entry to the file (newest on top, after the header):
--- captured: <ISO 8601 timestamp with timezone offset> processed: false mode: unknown --- <verbatim rant text> --- -
Confirm in one line:
Captured to brain/rants/<YYYY-MM-DD>.md. <N> rants today, M unprocessed.Do not summarise the rant content.
Step 2: Offer routing (optional)
On a second line, ask:
Want to act on it now? Say
decision,draft,plan, orlog- or ignore this and /dream will pick it up later.
The user may answer or may not. Either is fine. The rant is already on disk.
Step 3: If the user routes, act
If the user replies with one of the route words (or natural language that maps to one), update the rant entry's mode: field in brain/rants/<YYYY-MM-DD>.md to the chosen route, then invoke the matching skill:
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 · 67 lines · 51 tokens per session scan A f4bdd0d384c7
rant is a command published in the GitHub repository ARCASSystems/FounderOS (5 stars, last pushed 18d ago), licensed MIT. It adds 51 tokens to every session and 914 once invoked, about $0.0003 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.