PuPu: Skill for Claude Code

.agents/skills/release-operator/SKILL.md

release-operator is a skill for Claude Code, Codex from haoxiang-xu/PuPu. It costs 54 tokens per session (877 once invoked), scanned A, original, Apache-2.0.

A controlled operator for an existing GitHub Actions release process. GitHub Actions is GitHub's system for running automated tasks such as builds and releases.

In plain words
What is it for?
Use it to inspect, start, wait for, stage, resume, or publish a specific release workflow run.
Why use it?
It keeps release steps and approvals explicit, preventing accidental publishing, tagging, or moving to the next phase without the project owner's instruction.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is haoxiang-xu/PuPu's own configuration. It tells Claude Code and Codex how to work on PuPu itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything PuPu configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/release-qa/release-operator.mjs <command> ....

Reuse

Borrowing it

Nothing to install: this file belongs to haoxiang-xu/PuPu. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/haoxiang-xu/PuPu/main/.agents/skills/release-operator/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/haoxiang-xu/PuPu

Made for: Claude Code, Codex.

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.

agentmods badge for release-operator

README.md
[![agentmods](https://agentmods.dev/badge/skills/haoxiang-xu/pupu/release-operator/github.svg)](https://agentmods.dev/skills/haoxiang-xu/pupu/release-operator)
Your own site
<a href="https://agentmods.dev/skills/haoxiang-xu/pupu/release-operator"><img src="https://agentmods.dev/badge/skills/haoxiang-xu/pupu/release-operator/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.

agentmods 80×15 button for release-operator

Your own site · 80×15
<a href="https://agentmods.dev/skills/haoxiang-xu/pupu/release-operator"><img src="https://agentmods.dev/badge/skills/haoxiang-xu/pupu/release-operator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 877 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.00877
Opus 5 $0.00027 $0.00439
Sonnet 5 $0.00011 $0.00175
Haiku 4.5 $0.00005 $0.00088

Measured today against content hash 23dfab7fa1b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

release-operator 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.

.agents/skills/release-operator/SKILL.md · 79 lines

How it starts

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

PuPu Release Operator

Operate the existing release workflows through the deterministic repository CLI. This skill is an operator, not a release authority.

Authority boundary

  • Read-only plan, status, and wait may run without extra approval.
  • Immediately before every dispatch, state the exact phase, tag, commit/run inputs, and external effect, then obtain a fresh instruction from the project owner. Never carry approval from an earlier phase.
  • Never approve a GitHub Environment, move or create a tag, close an issue, change Project state, decide GO, or select a fuzzy latest run.
  • Stage creates or updates a Draft Release after protected approval. Publish makes that Draft public after a separate protected approval. Treat them as distinct mutations.
  • If the Release still has code to land, stop before Stage even when candidate and qualification are green.

Canonical CLI

Use only:

node scripts/release-qa/release-operator.mjs <command> ...

Commands:

  • plan: validate an exact phase/ref/input tuple without GitHub mutation.
  • dispatch: start one confirmed workflow and return its exact run ID/URL.
  • status: read one exact run ID and project its jobs/artifacts/blockers.
  • wait: resume observation of one exact run ID for a bounded period; it never retries or dispatches.

The CLI defaults waits to three hours and polls every 20 seconds. Increase the timeout only when the project owner wants continued monitoring; never shorten it merely to make a long packaging job fail sooner.

Phases

Candidate

Plan with the immutable release tag and full 40-character Unchain revision. Dispatch only after confirmation START_CANDIDATE.

node scripts/release-qa/release-operator.mjs plan --phase candidate --repo haoxiang-xu/PuPu --tag vX.Y.Z --unchain-ref <40-char-sha>

Qualification

For ordinary releases, use qualification with the exact successful candidate run ID and lower stable from-tag. For the frozen v0.1.10 baseline only, use bootstrap. Confirm with START_QUALIFICATION or START_BOOTSTRAP_QUALIFICATION respectively.

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

  1. today First seen · 79 lines · 54 tokens per session scan A 23dfab7fa1b0

Subscribe to this mod's changes

release-operator is a skill published in the GitHub repository haoxiang-xu/PuPu (36 stars, last pushed yesterday), licensed Apache-2.0. It adds 54 tokens to every session and 877 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-09-09.

Related

Other skills, from other repositories

release-readiness-check

Verify all prerequisites are met before a release by checking PRs, CI/CD status, environment health, and blocking issues across GitHub, ArgoCD, and Jira. Use before cutting a release, deploying to production, or during release planning.

caipe-io/ai-platform-engineering · 54 tokens

oma-dev-workflow

Use when setting up or optimizing developer workflows in a monorepo, managing mise tasks, git hooks, CI/CD pipelines, database migrations, or release automation. Invoke for development environment setup, build automation, testing workflows, and release coordination.

first-fluke/oh-my-agent · 53 tokens

b3os-release-ops

A release and deployment checklist for the b3os project. It covers merging code, live releases, urgent fixes, and changes to public Git history.

b3rys/b3rys-team-os · 113 tokens

skill-release-engineering

Prepara releases seguros com changelog, migrações, smoke tests, rollback, feature flags, CI e checklist operacional.

IAPro-Community/Orquestrador-Maestro · 30 tokens

merge-queue-thrash-stop-inflow-and-open-prs-as-drafts

When main moves faster than the slowest CI leg, every open branch goes stale before it can merge and the whole queue jams with nothing red. Use when: (1) several PRs sit at mergeStateStatus BEHIND with auto-merge armed and none of them lands; (2) branches are being updated, re-running CI and going stale again before…

wan-huiyan/agent-traffic-control · 285 tokens

github-actions

GitHub Actions workflow generator — CI/CD pipelines, releases, Docker builds, reusable workflows, composite actions, dependabot. Use for .github/workflows/ generation, debugging, and security hardening.

anilcancakir/claude-code-plugin · 43 tokens