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.
git clone --depth 1 https://github.com/brainOS-HQ/brain-osWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/brainos-hq/brain-os/decide)<a href="https://agentmods.dev/commands/brainos-hq/brain-os/decide"><img src="https://agentmods.dev/badge/commands/brainos-hq/brain-os/decide/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/brainos-hq/brain-os/decide"><img src="https://agentmods.dev/badge/commands/brainos-hq/brain-os/decide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00906 |
| Opus 5.5 | $0.00000 | $0.00362 |
| Sonnet 5.5 | $0.00000 | $0.00181 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
decide 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 1mo 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brain OS : Decision Capture
Capture a strategic decision so it never gets lost or reopened accidentally.
This is not /strategy (which helps you think a decision through). This captures the decision after it's been made.
REQUIRED FIRST READ
Before any tool call, read ~/.claude/brain-os/PROTOCOL.md. The protocol's "Tool routing" section is load-bearing: decision_check runs BEFORE any write.
Input
Arguments: $ARGUMENTS (format: <entity-name> "<decision summary>"). If no arguments, review what was decided this session and ask what to log.
Primary tool sequence
mcp__brain-os__decision_check(proposed_action, entity_id): conflict gate, runs FIRST- Gather details (see Step 2 below)
mcp__brain-os__decision_log(...): persist the decisionmcp__brain-os__entity_update(...): if the decision changesnext_moveor clears a blocker
Step 1: Conflict check
decision_check returns one of:
- clear : no conflict, proceed.
- caution : a related decision exists. Surface it, ask if this supersedes it.
- conflict : a contradictory active decision exists. STOP. Show the conflict and ask the user to confirm before proceeding.
Never log a conflict result without explicit user confirmation.
Step 2: Gather details
If a decision summary was provided, confirm and fill in gaps. If not, ask:
- What was decided?
- Why? (the real reason, not the polite one)
- What alternatives were considered, and why rejected?
- What's the proof action : one thing that validates this decision?
- When should this be reviewed?
One message, not an interrogation.
Step 3: Classify
Assign a decision type:
- product_direction : what to build, what the product is
- architecture : how to build it technically
- scope : what to include or cut
- priority : what to do first
- kill_park : stopping or pausing an entity or feature
- monetization : how to make money
- brand : identity, voice, positioning
Step 4: Log it
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.
- 1mo ago First seen · 100 lines · 0 tokens per session scan A dd799de5d3ea
decide is a command published in the GitHub repository brainOS-HQ/brain-os (6 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 906 tokens. 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
lians-audit
Run a Lians compliance/audit operation - snapshot, chain verify, backtest, or erasure.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.
slm-mesh
Cross-session peer coordination via the SLM mesh network. Lets multiple AI agent sessions on the same machine, and web apps the owner has allowed (ChatGPT, Claude on the web, Grok Bot, Muse, Composio), discover each other, send messages, wait for replies with meshwait, share lightweight state, and lock files to avoid…
slm-governance
Governed-workspace behavior for SuperLocalMemory. Covers roles (admin/member/viewer) and company mode, who administers a company-mode workspace (a signed-in admin, or slm team on the SLM computer), slm token show in strict mode, what remote web apps can never see or change, retention and lifecycle settings, the audit…
slm-bot-memory
Cross-bot memory on a shared computer (Grok Bot, Cursor plugin, any host where several agents share one machine). Explains agentid attribution vs. profile/scope access, how to namespace by agentid + profile + scope, and what must never be written to memory. Read this before the first remember/recall on a new…
slm-getting-started-bot
First-session orientation for SuperLocalMemory on a headless bot host (Grok Bot, or any Cursor-format plugin install with no hooks, no dashboard, and no interactive setup wizard). What is different here vs. Claude Code/Codex, which 19 tools are actually available, and the first three calls to make.