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.
git clone --depth 1 https://github.com/leaf76/session-collab-mcpWrote 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/leaf76/session-collab-mcp/end)<a href="https://agentmods.dev/commands/leaf76/session-collab-mcp/end"><img src="https://agentmods.dev/badge/commands/leaf76/session-collab-mcp/end/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/leaf76/session-collab-mcp/end"><img src="https://agentmods.dev/badge/commands/leaf76/session-collab-mcp/end.svg" alt="Reviewed on agentmods" width="80" 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.00009 | $0.00383 |
| Opus 5.5 | $0.00004 | $0.00153 |
| Sonnet 5.5 | $0.00002 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
end 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 1mo 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
End Session Collaboration
Properly terminate the current collaboration session.
Actions
1. Get Current Session Info
If session ID is not known, call mcp__session-collab__collab_session_list to find your session.
2. Check Unreleased Claims (IMPORTANT)
Before ending, call mcp__session-collab__collab_claim with:
action:"list"session_id: Your current session IDstatus: "active"
This shows all claims that will be released. Review them to decide if they should be marked as "complete" or "abandon".
3. End Session
Call mcp__session-collab__collab_session_end with:
session_id: Your current session IDrelease_claims:"complete"(mark work as done) or"abandon"(if work is incomplete)
Output Format
First show unreleased claims:
Unreleased Claims Review
| File/Symbol | Intent | Scope | Created |
|---|---|---|---|
path/to/file.ts |
Refactoring... | small | 2024-01-15 |
Then confirm session termination:
Session Ended
| Item | Value |
|---|---|
| Session ID | xxx |
| Session Name | name |
| Claims Released | N |
| Status | Completed / Abandoned |
Session collaboration has been terminated. All claims have been released.
Notes
- Always review claims before ending to ensure correct status
- Use
"complete"when you finished your work successfully - Use
"abandon"if you need to stop without finishing - Other sessions will be able to claim the released files
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.
- 1mo ago First seen · 59 lines · 9 tokens per session scan A ef98c8051d90
end is a command published in the GitHub repository leaf76/session-collab-mcp (2 stars, last pushed 3d ago), licensed MIT. It adds 9 tokens to every session and 383 once invoked, about $0.0000 per session on Opus 5.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
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
release
A typical CI release creates the release, associates commits, finalizes it, and records a deploy.
commit-push-pr
Commit, push, and open a PR (includes changeset creation).
check-browser
Use Browser Controller to check what's currently showing in my browser.
bulk-add
Batch-shelve several repos at once — from a URL list or your GitHub stars — then draft honest notes for each.