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 skills add cirwel/unitares --skill governance-lifecyclegit clone --depth 1 https://github.com/cirwel/unitaresWrote 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/skills/cirwel/unitares/governance-lifecycle)<a href="https://agentmods.dev/skills/cirwel/unitares/governance-lifecycle"><img src="https://agentmods.dev/badge/skills/cirwel/unitares/governance-lifecycle.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.1 | $0.00051 | $0.03888 |
| Opus 5 | $0.00026 | $0.01944 |
| Sonnet 5 | $0.00010 | $0.00778 |
| Haiku 4.5 | $0.00005 | $0.00389 |
Grade A, and why
governance-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 today.
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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Lifecycle
Last Updated: 2026-09-07
Primary Workflow Names
The core lifecycle should use primary task-verb tools. Each is implemented by a raw tool with the same identity rules and returns a normalized envelope with the operationally useful fields first (next_action, state_summary, risk_summary, memory_suggestions, recovery_hint). State-changing aliases preserve the full payload under raw_governance; read aliases default to a bounded lean/compact shape and explain how to request the full canonical payload. sync_state does not retrieve shared memory unless include_memory_suggestions=true is explicit.
| Task | Primary workflow tool | Raw implementation tool |
|---|---|---|
| Start a fresh process identity | start_session(force_new=true, ...) |
onboard |
| Check in after meaningful work | sync_state(response_text=..., complexity=...) |
process_agent_update |
| Check your working state | check_working_state() |
get_governance_metrics |
| Avoid duplicate work | search_shared_memory(query=...) |
knowledge(action="search") |
| Record what actually happened | record_result(...) |
outcome_event |
| Ask for a structured review | request_review(issue_description=...) |
dialectic(action="request") |
| Store a durable finding | store_finding(summary=..., discovery_type=...) |
knowledge(action="store") |
| Update a durable finding | update_finding(discovery_id=..., ...) |
knowledge(action="update") |
Use the primary workflow tools by default. Use raw implementation names only for older servers, compatibility code, or when you explicitly need the unwrapped handler response. start_session(force_new=true) is a process-start operation, not a per-turn continuation primitive. request_review reuses its issue_description as the thesis by default, so a lone review brief is actionable in one call. Pass explicit reasoning/root_cause to distinguish the position from the subject, or use_brief_as_thesis=false for the neutral two-call flow. Raw dialectic(action="request") remains two-call unless thesis fields or use_brief_as_thesis=true are supplied. Session reads carry plain-language whose_move/next_call guidance.
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.
- today Changed · +29 lines 68d6904d114d
- 8d ago First seen · 233 lines · 51 tokens per session scan A 95875ff856d7
governance-lifecycle is a skill published in the GitHub repository cirwel/unitares (4 stars, last pushed today), licensed Apache-2.0. It adds 51 tokens to every session and 3,888 once invoked, about $0.0003 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
adk-agent-builder
Builds ADK (Agent Development Kit) Python agents: LLM agents with tools, graph workflows of function and agent nodes, conditional routing, fan-out and join, schema-validated delegation between agents, human-in-the-loop pauses, and pytest coverage for all of it. Use when asked to create an agent or a workflow, add a…
adk-style
Python style and codebase conventions for ADK (Agent Development Kit): private-by-default file visibility, imports, type hints, Pydantic v2 models, formatting, docstrings, logging, async I/O, file and test layout, and unit test structure. Use when writing or editing ADK source or tests, deciding whether a new file or…
adk-verify-snippets
Checks that every Python code block in a Markdown file actually compiles and runs, by extracting each block to a temporary file, executing it in an isolated subprocess, and writing a pass/fail report with per-snippet coverage. Use when the user asks to verify, test, or validate the code samples in a README, a guide…
adk-setup
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test run. Runs only when explicitly requested, never on its own. Use when asked to set up, bootstrap, or repair a development…
python-best-practices
Provides Python patterns for type-first development with dataclasses, discriminated unions, NewType, and Protocol. Must use when reading or writing Python files.
Python Data Analysis
Clean datasets and create reproducible Python transformations and charts.