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/mrboups/xbrainWrote 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/mrboups/xbrain/settings)<a href="https://agentmods.dev/commands/mrboups/xbrain/settings"><img src="https://agentmods.dev/badge/commands/mrboups/xbrain/settings/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/mrboups/xbrain/settings"><img src="https://agentmods.dev/badge/commands/mrboups/xbrain/settings.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.00014 | $0.00227 |
| Opus 5.5 | $0.00006 | $0.00091 |
| Sonnet 5.5 | $0.00003 | $0.00045 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
gsd:settings 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.
This is a copy
89% identical to gsd:settings — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Routes to the settings workflow which handles:
- Config existence ensuring
- Current settings reading and parsing
- Interactive 5-question prompt (model, research, plan_check, verifier, branching)
- Config merging and writing
- Confirmation display with quick command references
<execution_context> @D:/VSC/xbrain/.claude/get-shit-done/workflows/settings.md </execution_context>
The workflow handles all logic including:
- Config file creation with defaults if missing
- Current config reading
- Interactive settings presentation with pre-selection
- Answer parsing and config merging
- File writing
- Confirmation display
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 · 37 lines · 14 tokens per session scan A 9cc153616e4a
gsd:settings is a command published in the GitHub repository mrboups/xbrain (2 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 227 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to gsd:settings, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
pensyve
Route explicit Pensyve memory requests through the bundled MCP server; supports recall, remember, observe, inspect, status, review, forget, and mention-style guidance.
inspect
View all memories stored for an entity in Pensyve.
recall
Search Pensyve memory by semantic similarity and text matching.
using-pensyve
Show available Pensyve memory tools, skills, and commands.
consolidate
Explain consolidation and the available Python or REST options.
forget
Delete all memories for an entity from Pensyve.