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/workstreamsgit 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/workstreams)<a href="https://agentmods.dev/commands/mrboups/xbrain/workstreams"><img src="https://agentmods.dev/badge/commands/mrboups/xbrain/workstreams.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.00025 | $0.00542 |
| Opus 5 | $0.00013 | $0.00271 |
| Sonnet 5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
gsd:workstreams 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
88% identical to gsd:workstreams — 9 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gsd-workstreams
Manage parallel workstreams for concurrent milestone work.
Usage
/gsd-workstreams [subcommand] [args]
Subcommands
| Command | Description |
|---|---|
list |
List all workstreams with status |
create <name> |
Create a new workstream |
status <name> |
Detailed status for one workstream |
switch <name> |
Set active workstream |
progress |
Progress summary across all workstreams |
complete <name> |
Archive a completed workstream |
resume <name> |
Resume work in a workstream |
Step 1: Parse Subcommand
Parse the user's input to determine which workstream operation to perform.
If no subcommand given, default to list.
Step 2: Execute Operation
list
Run: gsd-sdk query workstream.list --raw --cwd "$CWD"
Display the workstreams in a table format showing name, status, current phase, and progress.
create
Run: gsd-sdk query workstream.create <name> --raw --cwd "$CWD"
After creation, display the new workstream path and suggest next steps:
/gsd-new-milestone --ws <name>to set up the milestone
status
Run: gsd-sdk query workstream.status <name> --raw --cwd "$CWD"
Display detailed phase breakdown and state information.
switch
Run: gsd-sdk query workstream.set <name> --raw --cwd "$CWD"
Also set GSD_WORKSTREAM for the current session when the runtime supports it.
If the runtime exposes a session identifier, GSD also stores the active workstream
session-locally so concurrent sessions do not overwrite each other.
progress
Run: gsd-sdk query workstream.progress --raw --cwd "$CWD"
Display a progress overview across all workstreams.
complete
Run: gsd-sdk query workstream.complete <name> --raw --cwd "$CWD"
Archive the workstream to milestones/.
resume
Set the workstream as active and suggest /gsd-resume-work --ws <name>.
Step 3: Display Results
Format the JSON output from gsd-sdk query into a human-readable display.
Include the ${GSD_WS} flag in any routing suggestions.
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 · 70 lines · 25 tokens per session scan A 61faa6e4505c
gsd:workstreams is a command published in the GitHub repository mrboups/xbrain (2 stars, last pushed 22d ago), licensed MIT. It adds 25 tokens to every session and 542 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to gsd:workstreams, differing in 9 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.
recall
Search Pensyve memory by semantic similarity and text matching.
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.