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/anamized/server-os/multi-agent-workflownpx skills add ANAMIZED/Server-OS --skill multi-agent-workflowgit clone --depth 1 https://github.com/ANAMIZED/Server-OSWhat 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.00015 | $0.00136 |
| Opus 5 | $0.00008 | $0.00068 |
| Sonnet 5 | $0.00003 | $0.00027 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
multi-agent-workflow 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 19 lines · 15 tokens per session scan A 47b58779a281
multi-agent-workflow is a skill published in the GitHub repository ANAMIZED/Server-OS (1 stars, last pushed 6d ago), with no licence file. It adds 15 tokens to every session and 136 once invoked, about $0.0001 per session on Opus 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 skills, from other repositories
multi-agent-workflow
Planner → workers → critic loop for SuperAgenticMCP missions. Use when coordinating multi-step agent work across racked MCP servers.
multi-agent-workflow
Orchestrate sequential multi-agent workflows under a shared budget on OpenMesha. Use when a goal needs planner/researcher/worker roles or council-style decomposition.
routing-capability
Capability-first routing with latency tie-break for racked MCP servers. Use when selecting which server handles a tool call.
superagenticmcp
SuperAgenticMCP — the switchboard for your agent swarm. MCP-native router and multi-agent control plane that plans tasks, routes tool calls to racked MCP servers by capability and latency, streams execution, and files results into a memory-scope graph. Use when the user needs multi-agent orchestration over MCP, a…
memory-scope
Memory-scope constellation: persist run artifacts as a linked graph for later retrieval and board visualization.
Subagent Driven Development
Orchestrate specialized, autonomous AI agents to execute parallel subtasks with strict boundaries.