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/iii-experimental/agentos/lifecyclenpx skills add iii-experimental/agentos --skill lifecyclegit clone --depth 1 https://github.com/iii-experimental/agentosWhat 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.00013 | $0.00190 |
| Opus 5 | $0.00006 | $0.00095 |
| Sonnet 5 | $0.00003 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade B, and why
lifecycle scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
- Transition: `curl -X POST http://localhost:3111/api/lifecycle/transition -H 'Content-Type: application/json' -d '{"agentId": "claude-code", "newState": "working"}'` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Transition: `curl -X POST http://localhost:3111/api/lifecycle/transition -H 'Content-Type: application/json' -d '{"agentId": "claude-code", "newState": "working"}'` What it actually says
Manage agent session lifecycle:
- Transition:
curl -X POST http://localhost:3111/api/lifecycle/transition -H 'Content-Type: application/json' -d '{"agentId": "claude-code", "newState": "working"}' - Get state:
curl http://localhost:3111/api/lifecycle/state/claude-code - Add reaction:
curl -X POST http://localhost:3111/api/lifecycle/reactions -H 'Content-Type: application/json' -d '{"agentId": "claude-code", "from": "blocked", "to": "working", "action": "notify"}'
States: spawning -> working -> blocked -> pr_open -> review -> merged -> done | failed -> recovering | terminated.
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 · 15 lines · 13 tokens per session scan B 1764b11d5f22
lifecycle is a skill published in the GitHub repository iii-experimental/agentos (162 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 190 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
python-package-management
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
verify-samples-tool
How to use the verify-samples tool to run, verify, and manage sample definitions in the Agent Framework repository. Use this when adding, updating, or running sample verification.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.