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/autonomousgit 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.00020 | $0.00465 |
| Opus 5 | $0.00010 | $0.00233 |
| Sonnet 5 | $0.00004 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
gsd:autonomous 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
Uses ROADMAP.md phase discovery and Skill() flat invocations for each phase command. After all phases complete: milestone audit → complete → cleanup.
Creates/Updates:
.planning/STATE.md— updated after each phase.planning/ROADMAP.md— progress updated after each phase- Phase artifacts — CONTEXT.md, PLANs, SUMMARYs per phase
After: Milestone is complete and cleaned up.
<execution_context> @D:/VSC/xbrain/.claude/get-shit-done/workflows/autonomous.md @D:/VSC/xbrain/.claude/get-shit-done/references/ui-brand.md </execution_context>
Project context, phase list, and state are resolved inside the workflow using init commands (gsd-sdk query init.milestone-op, gsd-sdk query roadmap.analyze). No upfront context loading 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 · 47 lines · 20 tokens per session scan A b0fd19609181
gsd:autonomous is a command published in the GitHub repository mrboups/xbrain (2 stars, last pushed 18d ago), licensed MIT. It adds 20 tokens to every session and 465 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.
recall
Search Pensyve memory by semantic similarity and text matching.
using-pensyve
Show available Pensyve memory tools, skills, and commands.
forget
Delete all memories for an entity from Pensyve.
inspect
View all memories stored for an entity in Pensyve.