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/wybe-labs/session-multiplayerWrote 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/wybe-labs/session-multiplayer/sm-join)<a href="https://agentmods.dev/commands/wybe-labs/session-multiplayer/sm-join"><img src="https://agentmods.dev/badge/commands/wybe-labs/session-multiplayer/sm-join/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/wybe-labs/session-multiplayer/sm-join"><img src="https://agentmods.dev/badge/commands/wybe-labs/session-multiplayer/sm-join.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.00012 | $0.00075 |
| Opus 5.5 | $0.00005 | $0.00030 |
| Sonnet 5.5 | $0.00002 | $0.00015 |
| Haiku 4.5 | $0.00001 | $0.00007 |
Grade A, and why
sm-join 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
Use the session-multiplayer MCP server's join_room tool with the code "$ARGUMENTS". It can take up to 90 seconds to pair. When it succeeds, confirm which room I joined and check for any messages already waiting with check_messages.
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 · 7 lines · 12 tokens per session scan A 1dad8c0ecb05
sm-join is a command published in the GitHub repository wybe-labs/session-multiplayer (4 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 75 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
sim
Run the EmbodiedGen simulation rendering workflow with sim-cli.
cert-check
Review the current state against certification and platform compliance expectations.
combat-design
Design or revise combat rules, variables, readability, and tuning direction.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
web-build-fix
Diagnose and resolve web build, bundling, or deployment issues.
tech-debt
Track and prioritize technical debt.