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.
curl -O https://raw.githubusercontent.com/haoxiang-xu/PuPu/main/.agents/skills/release-close-sprint/SKILL.mdgit clone --depth 1 https://github.com/haoxiang-xu/PuPuWrote 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/haoxiang-xu/pupu/release-close-sprint)<a href="https://agentmods.dev/skills/haoxiang-xu/pupu/release-close-sprint"><img src="https://agentmods.dev/badge/skills/haoxiang-xu/pupu/release-close-sprint/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/haoxiang-xu/pupu/release-close-sprint"><img src="https://agentmods.dev/badge/skills/haoxiang-xu/pupu/release-close-sprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.01285 |
| Opus 5.5 | $0.00028 | $0.00514 |
| Sonnet 5.5 | $0.00014 | $0.00257 |
| Haiku 4.5 | $0.00007 | $0.00128 |
Grade A, and why
release-close-sprint 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 1mo 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release: Close
Administrative wrap-up, not deep QA or a substitute for release certification. The only scope is one Size=Release parent and its direct sub-issues in PUPU Project. Do not read or update a sprint document.
Plumbing: follow the shared board rules. All decisions, test evidence, waivers, and growth baseline live in GitHub comments on the Release parent or relevant child issue.
Acts
Act 1 — resolve and roll-call. Resolve the explicit open Release parent; zero or multiple matches requires the project owner's choice. Keep it In Progress while you paginate its direct sub-issues. For each child, verify both GitHub issue state=closed and Project Status=Done. A ticket labelled new feature also needs a fresh release-feature-audit:v2 comment naming this parent, Overall=PASS, and a Candidate digest equal to its delivered candidate; a waiver instead needs the full release-audit-waiver:v2 record on both child and parent. Do not accept free-text comments as evidence. A child without a work-type label blocks the roll-call until the project owner classifies it. Do not deep-review implementation here.
For any open child, the project owner chooses one disposition:
- Must ship: keep it attached; the Release cannot close.
- Defer: comment ticket, reason, destination, and project owner decision on the parent first; then remove it or attach it to a named future Release.
- Cancel: record the project owner's decision, remove the child from this Release, and, if requested, close it as not planned. Never use Project Status=Done to represent canceled work.
Never close a parent while it still owns an open child. Only after required scope is complete may the parent move to In Review. A must-ship child or a new must-fix child keeps or returns the parent to In Progress before any scope change.
Act 2 — smoke via real app. Follow the PuPu Test API reference with a real LLM (convention: openai:gpt-4.1, never local ollama). Cover chat lifecycle, message send, model/toolkit switch, and one probe through every affected area. Delete probe sessions. If Python changed, restart the sidecar before testing.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +12 lines f3f8163b6f4f
- 1mo ago First seen · 90 lines · 70 tokens per session scan A 4d1861d73aa7
release-close-sprint is a skill published in the GitHub repository haoxiang-xu/PuPu (36 stars, last pushed 3d ago), licensed Apache-2.0. It adds 70 tokens to every session and 1,285 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
operating-github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
testdino-releases
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers listreleases, getrelease, createrelease, and updaterelease. Accepts counter-style IDs like MS-12.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.