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/healthgit 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/health)<a href="https://agentmods.dev/commands/mrboups/xbrain/health"><img src="https://agentmods.dev/badge/commands/mrboups/xbrain/health.svg" alt="Measured on agentmods" 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 | $0.00014 | $0.00293 |
| Opus 5 | $0.00007 | $0.00147 |
| Sonnet 5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
gsd:health 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 4d 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.
What it actually says
--context runs an orthogonal check: the running session's context utilization. The workflow asks for the model's tokensUsed + contextWindow, calls gsd-sdk query validate.context, and renders one of three states:
| Utilization | State | Action |
|---|---|---|
| < 60% | healthy | no action — context is comfortable |
| 60% – 70% | warning | recommend /gsd-thread to start fresh |
| ≥ 70% | critical | reasoning quality may degrade past the fracture point |
<execution_context> @D:/VSC/xbrain/.claude/get-shit-done/workflows/health.md </execution_context>
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.
- 4d ago First seen · 31 lines · 14 tokens per session scan A d12cb603d740
gsd:health is a command published in the GitHub repository mrboups/xbrain (2 stars, last pushed 20d ago), licensed MIT. It adds 14 tokens to every session and 293 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
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.
consolidate
Run memory consolidation to promote, decay, and archive memories.
forget
Delete all memories for an entity from Pensyve.
inspect
View all memories stored for an entity in Pensyve.
memory-status
Show Pensyve memory namespace statistics and health overview.