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/pr-branchgit 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/pr-branch)<a href="https://agentmods.dev/commands/mrboups/xbrain/pr-branch"><img src="https://agentmods.dev/badge/commands/mrboups/xbrain/pr-branch.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.1 | $0.00024 | $0.00197 |
| Opus 5 | $0.00012 | $0.00098 |
| Sonnet 5 | $0.00005 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
gsd:pr-branch 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.
This is a copy
86% identical to gsd:pr-branch — 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
This solves the problem of PR diffs being cluttered with PLAN.md, SUMMARY.md, STATE.md changes that are irrelevant to code review.
<execution_context> @D:/VSC/xbrain/.claude/get-shit-done/workflows/pr-branch.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.
- 2d ago First seen · 26 lines · 24 tokens per session scan A 632ec79117dd
gsd:pr-branch is a command published in the GitHub repository mrboups/xbrain (2 stars, last pushed 21d ago), licensed MIT. It adds 24 tokens to every session and 197 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to gsd:pr-branch, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
title-commit
Stage the files belonging to the current change theme and propose a commit title (does NOT commit).
dream-apply
Walk a dream proposal artifact, review each item, apply accepted ones, commit.
using-pensyve
Show available Pensyve memory tools, skills, and commands.
pensyve
Route explicit Pensyve memory requests through the bundled MCP server; supports recall, remember, observe, inspect, status, review, forget, and mention-style guidance.
consolidate
Run memory consolidation to promote, decay, and archive memories.
inspect
View all memories stored for an entity in Pensyve.