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 skills add nexus-research-lab/nexus --skill room-playbookgit clone --depth 1 https://github.com/nexus-research-lab/nexusWrote 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/skills/nexus-research-lab/nexus/room-playbook)<a href="https://agentmods.dev/skills/nexus-research-lab/nexus/room-playbook"><img src="https://agentmods.dev/badge/skills/nexus-research-lab/nexus/room-playbook/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/skills/nexus-research-lab/nexus/room-playbook"><img src="https://agentmods.dev/badge/skills/nexus-research-lab/nexus/room-playbook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.00408 |
| Opus 5.5 | $0.00010 | $0.00163 |
| Sonnet 5.5 | $0.00005 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
room-playbook 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
Room Collaboration Playbook
Use this playbook for lightweight Room collaboration. The member handling the user request is the coordinator and final publisher; other members contribute or review when invited. A task-specific Room Skill may replace these roles with a more precise workflow.
Rules
- The coordinator states the objective, integrates contributions, resolves disagreements, and publishes the final answer. Contributors return evidence or a concrete result; they do not assume they own final publication.
- Do not leak private-context information into the public feed. For private
collection, use
send_messagewithdestination=current_room,visibility=private, explicit recipients,wake_policy=immediate, andreply_route=private. Setnext_reply_route=publiconly when the coordinator should naturally publish the synthesized result. - Treat public
@memberas conversation wake only. When durable ownership, delivery, dependency, recovery, or acceptance is required, materialize a WorkGraph and useassign_work; finish withsubmit_workandreview_work. - For serial conversation workflows, wake only the next member. For parallel accountable work, create separate Work Items and do not assume completion order.
- The coordinator stops once the objective is satisfied and no member has a new
action. A member woken without a useful contribution emits
<nexus_room_no_reply/>instead of a filler message. - If a member fails, times out, or is unavailable, the coordinator either
continues with available evidence, reassigns managed work through WorkGraph
controls, or reports the concrete blocker. Do not wait indefinitely or use a
raw
@to disguise failed durable responsibility.
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 · 40 lines · 24 tokens per session scan A aaec43bec17c
room-playbook is a skill published in the GitHub repository nexus-research-lab/nexus (155 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 408 once invoked, about $0.0001 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-30.
Other skills, from other repositories
agentscope-java
Expert Java developer skill for AgentScope Java framework - a reactive, message-driven multi-agent system built on Project Reactor. Use when working with reactive programming, LLM integration, agent orchestration, multi-agent systems, or when the user mentions AgentScope, ReActAgent, Mono/Flux, Project Reactor, or…
git-checkpoint
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
penguin-plugin
Use for workbenches — the tabs and pages beside the chat, with server code behind them, that an Agent keeps in its own workbenches/ folder inside PenguinHarness — building one, changing it, showing it as the whole app, restoring an earlier version, and removing a tab or a whole workbench when the user wants the custom…
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.
a2ui
Make a reply easier to read and act on with rich blocks inside ordinary Markdown — a choice the user picks from, a form that collects several answers, a procedure as steps with warnings in place, a callout, a Mermaid diagram, a weather card, a live clock or countdown, a dashboard of gauges for a quota, a budget or a…