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 agents/kivo360/omoios/phase3_multi_agent_coordination_completegit clone --depth 1 https://github.com/kivo360/OmoiOSWrote 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/agents/kivo360/omoios/phase3_multi_agent_coordination_complete)<a href="https://agentmods.dev/agents/kivo360/omoios/phase3_multi_agent_coordination_complete"><img src="https://agentmods.dev/badge/agents/kivo360/omoios/phase3_multi_agent_coordination_complete.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.04539 |
| Opus 5 | $0.00000 | $0.02269 |
| Sonnet 5 | $0.00000 | $0.00908 |
| Haiku 4.5 | $0.00000 | $0.00454 |
Grade A, and why
phase3_multi_agent_coordination_complete 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 647 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 3 Multi-Agent Coordination — COMPLETE ✅
Date: 2025-11-17
Status: ALL 4 ROLES IMPLEMENTED
Test Coverage: 171/171 passing (100%)
Summary
Phase 3 multi-agent coordination is fully implemented and production-ready. All four parallel work streams (Registry, Collaboration, Parallel Execution, Coordination Patterns) are complete with comprehensive test coverage.
Implementation Overview
✅ Role 1: Agent Registry (Capability-Aware Discovery)
Delivered:
- Agent model extensions (capabilities, capacity, health_status, tags)
- AgentRegistryService with CRUD + capability-based search
- Agent health monitoring with heartbeat tracking
- FastAPI endpoints for registration, search, health checks
- Migration 003_agent_registry with GIN indexes
- 17 tests (3 registry + 14 health)
Key Features:
- Capability matching with scoring algorithm
- Multi-dimensional ranking (overlap + availability + health + capacity)
- Event publishing for capability changes
- Stale agent detection (90s timeout)
Coverage: 89% (registry), 91% (health)
✅ Role 2: Collaboration Squad (Agent Communication)
Delivered:
- AgentMessage and CollaborationThread models
- CollaborationService for messaging + handoff protocol
- Thread management (create, list, close)
- Handoff workflow (request, accept, decline)
- FastAPI endpoints under
/api/v1/collaboration - Migration 004_collaboration_and_locking (agent_messages, collaboration_threads tables)
- 10 tests covering messaging, threads, handoffs
Key Features:
- Agent-to-agent messaging with read receipts
- Threaded conversations with participant tracking
- Task handoff protocol with accept/decline responses
- Event publishing (agent.message.sent, agent.handoff.requested, etc.)
- Broadcast support (to_agent_id = None)
Event Types:
agent.message.sentagent.collab.startedagent.collab.endedagent.handoff.requestedagent.handoff.acceptedagent.handoff.declined
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.
- 5d ago First seen · 647 lines · 0 tokens per session scan A a8e210a9b643
phase3_multi_agent_coordination_complete is an agent published in the GitHub repository kivo360/OmoiOS (75 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,539 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-30.
Other agents, from other repositories
assistant
You are a general-purpose assistant — the example agent that ships with Archie so a fresh install does something useful out of the box. You handle small, self-contained requests: summarizing a block of text, drafting a short reply, or explaining something plainly.
gatekeeper
You exist to exercise the MCP tool approval gate in end-to-end checks. When asked to call your tools, call them exactly as instructed and report exactly what they returned — no improvisation, no retries beyond what the instructions say.
pm
This is the example PM overlay. The text here is appended to the PM agent's system prompt, so use it to give the PM the standing context it needs for your organization — what the company/team does, who the regular requesters are, house style for replies, and any defaults that should hold across every conversation.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
annotator
Phase 2.5 전용 @AX 태그 스캔 및 적용 에이전트. executor가 수정한 파일 목록을 받아 @AX 태그를 자동으로 분석하고 적용한다.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…