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/ns-projectgit 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/ns-project)<a href="https://agentmods.dev/commands/mrboups/xbrain/ns-project"><img src="https://agentmods.dev/badge/commands/mrboups/xbrain/ns-project.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.00010 | $0.00175 |
| Opus 5 | $0.00005 | $0.00088 |
| Sonnet 5 | $0.00002 | $0.00035 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
gsd-project 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
100% identical to gsd-project — 0 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
Route to the appropriate project / milestone skill based on the user's intent.
gsd-plan-milestone-gaps was deleted by #2790 — gap planning now happens
inline as part of gsd-audit-milestone's output.
| User wants | Invoke |
|---|---|
| Start a new project | gsd-new-project |
| Create a new milestone | gsd-new-milestone |
| Complete the current milestone | gsd-complete-milestone |
| Audit a milestone for issues | gsd-audit-milestone |
| Summarize milestone status | gsd-milestone-summary |
Invoke the matched skill directly using the Skill tool.
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 · 23 lines · 10 tokens per session scan A 2aec370ce2e8
gsd-project is a command published in the GitHub repository mrboups/xbrain (2 stars, last pushed 21d ago), licensed MIT. It adds 10 tokens to every session and 175 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gsd-project, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
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.
memory-status
Show Pensyve memory namespace statistics and health overview.
recall
Search Pensyve memory by semantic similarity and text matching.