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/agent_lifecycle_managementgit 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/agent_lifecycle_management)<a href="https://agentmods.dev/agents/kivo360/omoios/agent_lifecycle_management"><img src="https://agentmods.dev/badge/agents/kivo360/omoios/agent_lifecycle_management.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.06217 |
| Opus 5 | $0.00000 | $0.03109 |
| Sonnet 5 | $0.00000 | $0.01243 |
| Haiku 4.5 | $0.00000 | $0.00622 |
Grade A, and why
agent_lifecycle_management 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 — 799 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Lifecycle Management Design Document
Created: 2025-11-20 Status: Draft Related: ../../requirements/agents/agent_lifecycle.md, ./multi_agent_orchestration.md, ../services/task_queue.md, ../monitoring/monitoring_architecture.md, ../monitoring/fault_tolerance.md
Document Overview
This design document specifies the architecture, components, protocols, and implementation patterns for managing the complete lifecycle of agents within the multi-agent orchestration system. It covers agent registration, heartbeat protocols, status transitions, resource allocation, termination procedures, and resurrection mechanisms.
Purpose: Provide a comprehensive design for agent lifecycle management that ensures reliable agent registration, monitoring, health checking, graceful termination, and recovery.
Target Audience: AI spec agents (Kiro, Cursor, Cline), implementation teams, system architects, DevOps engineers
Related Documents:
- Requirements Document - Source of truth for all requirements
- Multi-Agent Orchestration Design - Agent layer patterns and architecture
- Task Queue Management Design - Task assignment and agent interaction
- Monitoring Architecture Design - Health monitoring and anomaly detection
- Fault Tolerance Design - Failure detection and recovery procedures
Architecture Overview
High-Level Architecture
The Agent Lifecycle Management system consists of several key components that work together to manage agent registration, health monitoring, status transitions, and lifecycle events.
graph TB
subgraph "Agent Lifecycle Manager"
AR[Agent Registry]
HM[Heartbeat Manager]
SM[Status Manager]
RM[Resource Manager]
TM[Termination Manager]
end
subgraph "Agent Types"
WA[Worker Agents]
MA[Monitor Agents]
WDA[Watchdog Agents]
GA[Guardian Agent]
end
subgraph "Infrastructure"
EB[Event Bus]
SS[State Store]
MS[Metric Store]
end
WA -->|Register| AR
MA -->|Register| AR
WDA -->|Register| AR
GA -->|Register| AR
AR -->|Status Updates| SM
AR -->|Health Data| HM
AR -->|Resource Usage| RM
HM -->|Heartbeats| EB
SM -->|State Changes| SS
RM -->|Metrics| MS
EB -->|Events| WA
EB -->|Events| MA
EB -->|Events| WDA
EB -->|Events| GA
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 · 799 lines · 0 tokens per session scan A c6add29d8a8a
agent_lifecycle_management 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 6,217 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…