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 glassity/agent-skills --skill lifecycle-accept-plangit clone --depth 1 https://github.com/glassity/agent-skillsWrote 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/glassity/agent-skills/lifecycle-accept-plan)<a href="https://agentmods.dev/skills/glassity/agent-skills/lifecycle-accept-plan"><img src="https://agentmods.dev/badge/skills/glassity/agent-skills/lifecycle-accept-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.
<a href="https://agentmods.dev/skills/glassity/agent-skills/lifecycle-accept-plan"><img src="https://agentmods.dev/badge/skills/glassity/agent-skills/lifecycle-accept-plan.svg" alt="Reviewed on agentmods" width="80" 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.00070 | $0.01105 |
| Opus 5 | $0.00035 | $0.00553 |
| Sonnet 5 | $0.00014 | $0.00221 |
| Haiku 4.5 | $0.00007 | $0.00111 |
Grade A, and why
lifecycle-accept-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 8d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accept the plan — advance an assignment to execution
When to use
- The user has read the per-service brief in
project/<slug>-<service>.mdand refined it intoplan/<date>-<slug>-<service>.md. - The user says "accept the plan", "advance to execution", or similar.
- The assignment's
current_stageisalignment_step_2. This skill re-reads that from the server and stops if it moved.
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.
Resolving the assignment id
A managed Glassity workspace names the record the checkout belongs to in the environment. It is a convenience, not a requirement — the skill works the same without it.
Managed workspaces export the primary record's id as GLASSITY_ISLAND_ID;
when it is set and the user has not named a record, use it.
Otherwise use the id the user gave you. Either way, watch the prefix: an id
beginning with opportunity_ but not opportunity_assignment_ is an
opportunity, not an assignment — run
glassity --output=json opp show <opportunity-id> and take the assignment from
assignments[].prefix_id. If the user has not named anything and the env var
is unset, ask. Never abort merely because the environment does not identify a
record.
Pre-flight, no mutation
-
Re-read the authoritative state. State can move under the user between the moment they decide and the moment the request is sent, so read it again here rather than trusting anything from earlier in the session:
glassity --output=json opp show-assignment "<assignment-id>"If
current_stageis notalignment_step_2, orstateisarchived,rejected, orcompleted, render:The assignment moved under you (server says stage=
<X>, state=<Y>). Refresh and re-evaluate before retrying — nothing was mutated.
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.
- 8d ago First seen · 121 lines · 70 tokens per session scan A 57add7311639
lifecycle-accept-plan is a skill published in the GitHub repository glassity/agent-skills (2 stars, last pushed 26d ago), licensed Apache-2.0. It adds 70 tokens to every session and 1,105 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.