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-mark-pr-mergedgit 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-mark-pr-merged)<a href="https://agentmods.dev/skills/glassity/agent-skills/lifecycle-mark-pr-merged"><img src="https://agentmods.dev/badge/skills/glassity/agent-skills/lifecycle-mark-pr-merged/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-mark-pr-merged"><img src="https://agentmods.dev/badge/skills/glassity/agent-skills/lifecycle-mark-pr-merged.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.00089 | $0.01112 |
| Opus 5 | $0.00044 | $0.00556 |
| Sonnet 5 | $0.00018 | $0.00222 |
| Haiku 4.5 | $0.00009 | $0.00111 |
Grade A, and why
lifecycle-mark-pr-merged 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mark the PR merged — close the loop after the change lands
When to use
- The user implemented the refined plan in the target infrastructure repo, opened a pull request, and it has been merged through their normal review.
- The user says "mark the PR merged", "we shipped it", or pastes the PR URL.
- The assignment is at the
executionstage, statein_progress.
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>"Stop and say the assignment moved if it is no longer
in_progress. -
Get the pull request URL from the user. It must be the full
https://github.com/<owner>/<repo>/pull/<number>form — the server parses owner, repo, and number out of it. If the user only has a number, ask for the URL. -
Locate the plan at
plan/<date>-<slug>-<service>.md— the same file accepted inlifecycle-accept-plan— and capture its current commit sha. The plan supplies the target repository when the assignment does not already carry one. -
Make sure the pull request is registered.
/finops-executeregisters each PR when it is opened, so it is usually already there. If it was opened outside that flow, register it now — the server upserts on (repo, number), so re-running is safe:glassity pr register "<assignment-id>" \ --repo "<owner>/<repo>" --number <n> --title "<pr title>" --url "<pr-url>"This is a two-phase mutation like the rest.
Phase 1 — register the artifact, then transition
Step A — register the implementation plan with the PR
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 · 109 lines · 89 tokens per session scan A f6d7c085bd76
lifecycle-mark-pr-merged is a skill published in the GitHub repository glassity/agent-skills (2 stars, last pushed 28d ago), licensed Apache-2.0. It adds 89 tokens to every session and 1,112 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.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.