What is lifecycle-reject-plan?

A workflow for rejecting a proposed plan for one Glassity assignment, an individual piece of work within an opportunity. It records why the plan does not fit and moves the assignment to rejected.

Use it after reviewing a service brief when you decide not to execute it, providing a short reason for the rejection.

It prevents an unsuitable brief from moving forward without documenting the decision. It also checks that the assignment is still at the stage where rejection is allowed.

lifecycle-reject-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-reject-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-reject-plan/github.svg)](https://agentmods.dev/skills/glassity/agent-skills/lifecycle-reject-plan)

Your own site

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

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

When invoked 729 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.00078	$0.00729
Opus 5	$0.00039	$0.00365
Sonnet 5	$0.00016	$0.00146
Haiku 4.5	$0.00008	$0.00073

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

Security

Grade A, and why

lifecycle-reject-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 9d 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-reject-plan/SKILL.md · 86 lines

How it starts

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

Reject the plan — bow out of an assignment with a reason

When to use

The user has read the per-service brief in project/<slug>-<service>.md, talked it through, and decided it does not apply to their service.
The user says "reject the plan", "this brief doesn't fit my service", "skip this one".
The assignment's current_stage is alignment_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.

Pre-flight

Re-read the authoritative state:
```
glassity --output=json opp show-assignment "<assignment-id>"
```
If current_stage is not alignment_step_2, or state is already terminal, say the assignment moved under the user and stop.
Locate the brief:
```
ls project/*.md
```
It will be project/<slug>-<service>.md. Capture the commit that introduced it with git log -1 --format=%H -- project/<file>.
Ask for a one-line reason if the user has not given one. It lands on the status report and is how the leader spots a pattern of bad briefs.

Phase 1 — two mutations, chained

Step A — register the rejected brief

glassity --output=json opp register-assignment-artifact "<assignment-id>" \
  --kind plan \
  --stage alignment_step_2 \
  --path "project/<file>" \
  --commit-sha "<sha>" \
  --status rejected

Show the verbatim plan; wait for "yes".

Step B — transition to rejected

glassity --output=json opp transition "<assignment-id>" \
  --target-state rejected \
  --comment "<the user's reason>"

Show the verbatim plan; wait for "yes".

Errors

Same {error: {code, message, remediation}} envelope as lifecycle-accept-plan:

Read the full file on GitHub · 86 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.

9d ago First seen · 86 lines · 78 tokens per session scan A f39f310a5729

Subscribe to this mod's changes

lifecycle-reject-plan is a skill published in the GitHub repository glassity/agent-skills (2 stars, last pushed 27d ago), licensed Apache-2.0. It adds 78 tokens to every session and 729 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.

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

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens