rant

A command for saving a user's unstructured rant as a dated note before optionally directing it elsewhere.

In plain words
What is it for?
Use it to write rants into brain/rants/ by date, while removing text marked private. It can then offer to route the captured note.
Why use it?
It prevents long, unfocused thoughts from being lost while you decide later how they should be organized.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/arcassystems/founderos/rant
Clone the repo
git clone --depth 1 https://github.com/ARCASSystems/FounderOS

Made for: Claude Code.

Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 914 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00051 $0.00914
Opus 5 $0.00026 $0.00457
Sonnet 5 $0.00010 $0.00183
Haiku 4.5 $0.00005 $0.00091

Measured 2d ago against content hash f4bdd0d384c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.claude/commands/rant.md · 67 lines

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

  1. Read the user's rant text (whatever followed /rant or the natural-language trigger like "I want to rant" / "let me dump something").

  2. Determine today's date in the user's timezone. Look up timezone from core/identity.md. If not set, default to local system time.

  3. Determine the rants file path: brain/rants/<YYYY-MM-DD>.md.

  4. If the file does not exist, create it with this header:

    # Rants - <YYYY-MM-DD>
    
  5. 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."

  6. 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>
    
    ---
    
  7. 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, or log - 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:

Read the full file on GitHub · 67 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. 2d ago First seen · 67 lines · 51 tokens per session scan A f4bdd0d384c7

Subscribe to this mod's changes

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.