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_lifecyclegit clone --depth 1 https://github.com/kivo360/OmoiOSWhat 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.04333 |
| Opus 5 | $0.00000 | $0.02167 |
| Sonnet 5 | $0.00000 | $0.00867 |
| Haiku 4.5 | $0.00000 | $0.00433 |
Grade A, and why
agent_lifecycle 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.
How it starts
The opening of the file, as written. The whole thing — 544 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Lifecycle Management Requirements
Created: 2025-11-20 Status: Draft Purpose: Specify detailed requirements for the full lifecycle management of agents in the multi-agent orchestration system Related: docs/requirements/agents/multi_agent_orchestration.md
Document Overview
This document specifies detailed requirements for managing the complete lifecycle of agents within the multi-agent orchestration system. It covers agent registration, state transitions, heartbeat protocols, resource allocation, and graceful termination procedures.
Parent Document: Multi-Agent Orchestration Requirements
1. Agent Types and Classifications
1.1 Worker Agents
Worker agents are the primary executors of domain-specific tasks within the workflow pipeline.
REQ-AGENT-WORKER-001: Worker Agent Specialization
WHEN a worker agent is instantiated, THE SYSTEM SHALL assign exactly ONE phase specialization from the following set:
- PHASE_REQUIREMENTS: Requirements analysis and decomposition
- PHASE_IMPLEMENTATION: Code generation and modification
- PHASE_VALIDATION: Output verification and acceptance testing
- PHASE_ANALYSIS: Investigation and root cause analysis
- PHASE_TESTING: Comprehensive test execution
Rationale: Specialization ensures agents develop deep expertise in their domain, leading to higher quality outputs and more predictable behavior patterns.
Acceptance Criteria:
- Agent cannot be assigned tasks from phases outside its specialization
- Agent metadata includes phase_id as immutable property
- System rejects attempts to reassign agent specialization after instantiation
REQ-AGENT-WORKER-002: Worker Capability Declaration
WHEN a worker agent registers with the system, THE SYSTEM SHALL require the agent to declare its capabilities as a structured list including:
- Supported programming languages
- Framework expertise
- Tool proficiencies (e.g., specific MCP tools)
- Domain knowledge areas
- Maximum concurrent task capacity
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 · 544 lines · 0 tokens per session scan A 63371e9bcb89
agent_lifecycle 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,333 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
workflow-architect
工作流架构师，负责复杂业务流程设计、状态机建模、事件驱动架构和自动化编排方案.
performance-benchmarker
性能基准测试专家，负责性能瓶颈定位、负载测试、内存/CPU分析和性能回归检测.
sre
站点可靠性工程师，负责系统可用性保障、事故响应、容量规划、SLO/SLI定义和自动化运维.
api-tester
API测试专家，负责接口契约验证、边界条件测试、认证流程测试和API性能基准建立.
ai-engineer
AI/ML工程师，负责模型集成、提示工程、RAG管道、Agent工作流设计和AI功能开发，交付高质量的智能化功能模块.
backend-architect
Python/FastAPI后端架构师，负责API设计、数据库建模、系统架构搭建、性能优化、可扩展性设计，交付稳健可维护的后端服务.