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 skills/nodealchemy/powernode-platform/workspacenpx skills add nodealchemy/powernode-platform --skill workspacegit clone --depth 1 https://github.com/nodealchemy/powernode-platformWhat 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.00000 | $0.00813 |
| Opus 5 | $0.00000 | $0.00407 |
| Sonnet 5 | $0.00000 | $0.00163 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
workspace 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace Chat Operations
Manage Powernode workspace conversations — read, send, create, and administer multi-agent chat workspaces.
Routing
Determine the intent from the user's message (or the automated daemon trigger) and execute the appropriate operation.
Incoming Messages (default — no arguments)
When invoked with no arguments or by the SSE daemon:
- Read the
<workspace-messages>context injected by theUserPromptSubmithook - For each message requiring a response, reply via the
platform.send_messageMCP tool withconversation_idandmessageparams - Always acknowledge — never silently ignore workspace communications
- Process messages in chronological order
- After responding, continue with any current work in progress
Send a Message
When the user wants to send a message to a workspace:
| Tool | Parameters |
|---|---|
platform.send_message |
conversation_id (required), message (required) |
- Include
@AgentNamein message text to mention and notify specific agents - If the user doesn't specify a conversation, use the active conversation from
<workspace-messages>context or ask
List Workspaces
| Tool | Parameters |
|---|---|
platform.list_workspaces |
optional limit (default 10) |
Shows workspace conversations the current user participates in.
Read Message History
| Tool | Parameters |
|---|---|
platform.list_messages |
conversation_id, optional limit (default 20, max 100) |
Retrieve recent messages from a workspace conversation.
Create a Workspace
| Tool | Parameters |
|---|---|
platform.create_workspace |
name (required), optional agent_ids, optional include_concierge |
Creates a new workspace conversation. The calling MCP client agent is automatically added.
Invite an Agent
| Tool | Parameters |
|---|---|
platform.invite_agent |
conversation_id, agent_id (or "concierge" for default concierge) |
Add an agent to an existing workspace conversation.
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 · 96 lines · 0 tokens per session scan A 02b71a9b3d45
workspace is a skill published in the GitHub repository nodealchemy/powernode-platform (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 813 tokens. 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 skills, from other repositories
good-first-issue-batch
File a batch of contributor-ready GitHub issues from the seeds backlog, re-verifying every candidate against HEAD first so no dead issue reaches a contributor. Activate for prompts like "file some good first issues", "open a batch of GFIs", "publish backlog issues to GitHub", "find contributor-ready work", or after an…
seeds-issue-audit
Audit and triage open Seeds (sd) issues — find which can be closed, auto-close high-confidence completed ones, and report borderline cases. Activate for prompts like "audit open issues", "which seeds issues can be closed", "clean up the issue tracker", "triage the seeds backlog".
os-eco-dep-sync
Bump warren onto the latest published @os-eco/ versions across package.json + bun.lock and the Dockerfile CLI pins, then run the gates and open a PR. Use when checking if warren is on the newest burrow/plot/canopy/seeds/mulch/sapling.
release
Prepare, cut, and verify a warren release — tracker audits, version bump, CHANGELOG curation, ROADMAP update, push, then watch the pipeline through to published artifacts.
warren-dogfood-pipeline
Full prioritize → dispatch → shepherd → track pipeline against the live warren instance. Audits the seeds backlog around a focus theme, dispatches the surviving issues to warren agents one at a time, babysits the resulting PRs to merge (update-branch, conflict-repair runs, auto-merge), and closes the loop in the…
canvas
Display HTML content on connected Mayros nodes (Mac app, iOS, Android).