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 jrjsmrtn/project-orchestration-skills --skill wrapup-sprintgit clone --depth 1 https://github.com/jrjsmrtn/project-orchestration-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/jrjsmrtn/project-orchestration-skills/wrapup-sprint)<a href="https://agentmods.dev/skills/jrjsmrtn/project-orchestration-skills/wrapup-sprint"><img src="https://agentmods.dev/badge/skills/jrjsmrtn/project-orchestration-skills/wrapup-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/jrjsmrtn/project-orchestration-skills/wrapup-sprint"><img src="https://agentmods.dev/badge/skills/jrjsmrtn/project-orchestration-skills/wrapup-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.00063 | $0.04535 |
| Opus 5 | $0.00032 | $0.02268 |
| Sonnet 5 | $0.00013 | $0.00907 |
| Haiku 4.5 | $0.00006 | $0.00453 |
Grade A, and why
wrapup-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 12d 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 — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrap Up Sprint
Complete a sprint with retrospective, changelog update, and release tagging.
When to Use
- When all planned work in a sprint is completed or explicitly deferred
- At the end of a sprint cycle
- Before starting a new sprint
Required Inputs
- Sprint number (e.g., 3)
- Version to release (e.g., 0.1.5)
In the commands below, substitute the placeholders throughout: NNNN is the zero-padded
sprint number in filenames (e.g. sprint-0003-plan.md), N is the bare sprint number in
messages (e.g. Sprint 3), and 0.1.x / 0.1.y are the version being released and the
previous version (e.g. 0.1.5 / 0.1.4). They are not literal.
Prerequisites
Before running this skill, verify:
- All planned work is complete OR explicitly deferred
- All tests passing
- Pre-commit and pre-push hooks pass
Workflow
Step 1: Review Sprint Plan
Read the sprint plan to understand what was committed:
cat docs/sprints/sprint-NNNN-plan.md
Identify:
- What was delivered
- What was dropped or deferred (and why)
- Key decisions or insights from the sprint
Step 2: Update Sprint Plan Status
Mark the sprint plan as complete. Update the status field and check off completed acceptance criteria.
Step 3: Create Sprint Retrospective
Two formats are available. Choose based on sprint complexity:
- Minimal — for routine sprints, single-feature sprints, or sprints without notable issues (default)
- Expanded — for integration work, multi-sprint efforts, or sprints with notable challenges
Create docs/sprints/sprint-NNNN-retrospective.md (markdown) or sprint-NNNN-retrospective.yml (YAML):
Minimal Format (Markdown)
# Sprint [N] Retrospective
**Delivered**: yes / partial / no — [one line summary]
**Dropped**: [anything intentionally cut, and why — or "nothing"]
**Key insight**: [one thing learned that future sprints should know]
**Next candidate**: [what this sprint implies about what comes next]
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.
- 12d ago First seen · 410 lines · 63 tokens per session scan A 2b3d9ca6f339
wrapup-sprint is a skill published in the GitHub repository jrjsmrtn/project-orchestration-skills (15 stars, last pushed 7d ago), licensed MIT. It adds 63 tokens to every session and 4,535 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-30.
Other skills, from other repositories
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
flow-next-land
Autonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LANDVERDICT. Use when asked to land PRs.
last-tag
Show commits since the last tag in a formatted table. Use when user asks "what changed since last release", "commits since last tag", "last-tag", "what's new", or wants to see recent unreleased changes.
re0-release
Walk a pending change through this repo's shipping and releasing checklist end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.
plugin-publish
A release guide for publishing Zhin.js plugins to npm, the JavaScript package registry, and to the Zhin plugin marketplace. It covers package metadata, versioning, release checks, and submission requirements.
ship
Ship a build — pre-flight checks, deploy, document, verify, monitor. Use when deploying code, publishing packages, or releasing.