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/mrboups/xbrain/configgit clone --depth 1 https://github.com/mrboups/xbrainWhat 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.00022 | $0.00651 |
| Opus 5 | $0.00011 | $0.00326 |
| Sonnet 5 | $0.00004 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
gsd:config 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 yesterday.
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.
What it actually says
Mode routing:
- default (no flag): Common-case toggles (model, research, plan_check, verifier, branching) → settings workflow
- --advanced: Power-user knobs (planning tuning, timeouts, branch templates, cross-AI execution) → settings-advanced workflow
- --integrations: Third-party API keys, code-review CLI routing, agent-skill injection → settings-integrations workflow
- --profile : Switch model profile (quality|balanced|budget|inherit) → set-profile (inline)
| Flag | Action | Workflow |
|---|---|---|
| (none) | Interactive 5-question common-case config prompt | settings |
| --advanced | Power-user knobs: planning, execution, discussion, cross-AI, git, runtime | settings-advanced |
| --integrations | API keys (Brave/Firecrawl/Exa), review CLI routing, agent skills | settings-integrations |
| --profile <name> | Switch model profile without interactive prompt | gsd-sdk config-set-model-profile |
<execution_context> @D:/VSC/xbrain/.claude/get-shit-done/workflows/settings.md @D:/VSC/xbrain/.claude/get-shit-done/workflows/settings-advanced.md @D:/VSC/xbrain/.claude/get-shit-done/workflows/settings-integrations.md </execution_context>
Parse the first token of $ARGUMENTS:
- If it is
--advanced: strip the flag, execute settings-advanced workflow - If it is
--integrations: strip the flag, execute settings-integrations workflow - If it starts with
--profile: extract the profile name (remainder after--profile), then:- Pre-flight check (#2439): verify
gsd-sdkis on PATH viacommand -v gsd-sdk. If absent, emit the install hintInstall GSD via 'npm i -g get-shit-done'and stop — do NOT invokegsd-sdkdirectly (avoids the opaquecommand not found: gsd-sdkfailure). - Run:
gsd-sdk query config-set-model-profile <profile-name> --rawand display the output verbatim.
- Pre-flight check (#2439): verify
- Otherwise: execute settings workflow (no argument needed)
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.
- yesterday First seen · 58 lines · 22 tokens per session scan A 635acf54017f
gsd:config is a command published in the GitHub repository mrboups/xbrain (2 stars, last pushed 18d ago), licensed MIT. It adds 22 tokens to every session and 651 once invoked, about $0.0001 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
slm-loop
Run a task as a bounded, gate-verified loop backed by SuperLocalMemory — iterate until an independent gate passes, never on the agent's own claim.
pensyve
Route explicit Pensyve memory requests through the bundled MCP server; supports recall, remember, observe, inspect, status, review, forget, and mention-style guidance.
using-pensyve
Show available Pensyve memory tools, skills, and commands.
inspect
View all memories stored for an entity in Pensyve.
memory-status
Show Pensyve memory namespace statistics and health overview.
recall
Search Pensyve memory by semantic similarity and text matching.