What is lifecycle-approve-plan?

An approval workflow for an organization-wide execution plan in Glassity, a platform for coordinating FinOps work across services.

Use it to approve a written plan, distribute work to service owners, and seed their individual assignments.

It checks that the opportunity is still at the right stage before approving the plan and creating assignments for service teams.

lifecycle-approve-plan — Skill for Claude Code by glassity

Install

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.

Any agent

npx skills add glassity/agent-skills --skill lifecycle-approve-plan

Clone the repo

git clone --depth 1 https://github.com/glassity/agent-skills

Made for: Claude Code.

Or install glassity, the plugin that ships this one along with the rest of its 19 skills, 6 commands, 2 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/glassity/agent-skills/lifecycle-approve-plan/github.svg)](https://agentmods.dev/skills/glassity/agent-skills/lifecycle-approve-plan)

Your own site

<a href="https://agentmods.dev/skills/glassity/agent-skills/lifecycle-approve-plan"><img src="https://agentmods.dev/badge/skills/glassity/agent-skills/lifecycle-approve-plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/glassity/agent-skills/lifecycle-approve-plan"><img src="https://agentmods.dev/badge/skills/glassity/agent-skills/lifecycle-approve-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,073 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00089	$0.01073
Opus 5	$0.00044	$0.00536
Sonnet 5	$0.00018	$0.00215
Haiku 4.5	$0.00009	$0.00107

Measured 10d ago against content hash 8605cefcaedb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

lifecycle-approve-plan 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 10d 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.

skills/lifecycle-approve-plan/SKILL.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Approve the org plan and seed assignments

When to use

On the opportunity, not an assignment. The leader has written the organization-wide execution plan and triaged out assignments that do not apply.
The opportunity's current_stage is alignment_step_1. This skill re-reads that from the server and stops if it moved.
The user says "approve the plan", "distribute to the teams", "seed the assignments".

This is the opportunity-level half of alignment. Its per-service half — a service owner accepting their refined brief — is lifecycle-accept-plan.

Binary check

Run command -v glassity before the first CLI call. If it is missing, stop and tell the user to install it with brew install glassity/tap/glassity or from https://github.com/glassity/cli/releases. No account yet? Sign up at app.glassity.cloud.

Pre-flight, no mutation

Re-read the authoritative state, because it can move between the moment the leader decides and the moment the request is sent:
```
glassity --output=json opp show "<opportunity-id>"
```
If current_stage is not alignment_step_1, or the plan is already approved, render:

The opportunity moved under you (server says stage=<X>). Refresh and re-evaluate before retrying — nothing was mutated.

Stop. Do not redeem any token.
Locate the org plan. The server pins the newest file matching plans/*-plan.md:
```
ls plans/*-plan.md
```
If there is none, stop and write plans/<YYYY-MM-DD>-<slug>-plan.md first. It carries the how: per-account decisions, recipients, thresholds, module structure, and the per-team checklist.
Commit the plan. Approval pins the plan's commit, so it has to be committed on the branch the server reads before you approve:
```
git add plans/<file>
git commit -m "Org execution plan"
```

Read the full file on GitHub · 112 lines

Changes

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.

10d ago First seen · 112 lines · 89 tokens per session scan A 8605cefcaedb

Subscribe to this mod's changes

lifecycle-approve-plan is a skill published in the GitHub repository glassity/agent-skills (2 stars, last pushed 27d ago), licensed Apache-2.0. It adds 89 tokens to every session and 1,073 once invoked, about $0.0004 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.

Planning Project management

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens