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 Mr-pixle/jira-mcp --skill release-checklistgit clone --depth 1 https://github.com/Mr-pixle/jira-mcpWrote 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/mr-pixle/jira-mcp/release-checklist)<a href="https://agentmods.dev/skills/mr-pixle/jira-mcp/release-checklist"><img src="https://agentmods.dev/badge/skills/mr-pixle/jira-mcp/release-checklist/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/mr-pixle/jira-mcp/release-checklist"><img src="https://agentmods.dev/badge/skills/mr-pixle/jira-mcp/release-checklist.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.00094 | $0.01057 |
| Opus 5 | $0.00047 | $0.00528 |
| Sonnet 5 | $0.00019 | $0.00211 |
| Haiku 4.5 | $0.00009 | $0.00106 |
Grade A, and why
release-checklist 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 11d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Checklist
Keywords
release readiness, can we ship, release notes, close the version, release checklist, what is blocking the release, cut the release, version closeout, آمادگی انتشار, یادداشت انتشار, بستن نسخه
Take a version from "are we ready?" through to "it is released and the leftovers have somewhere to go".
Changes data at the final steps only, and Project.release_version previews first under the default policy.
Workflow
Step 1 — Find the version
Project.get_versions with released=false lists the candidates. If the user named a version that does not exist, the error lists the real ones — use that rather than guessing at a typo.
Note whether the version is already marked overdue. A planned release date that has passed belongs in the summary.
Step 2 — Assess
Report.release_readiness gives the verdict, the completion percentage, and the three lists that matter: unresolved issues, open defects, and blocked items.
Lead with the caveat this report carries: it only sees issues tagged with the fixVersion. Work belonging to the release but never tagged is invisible. Before trusting a green result, sanity-check it:
project = OPS AND resolutiondate >= -30d AND fixVersion is EMPTY
Recently completed work with no fixVersion is either unrelated or was forgotten. Worth thirty seconds to check.
Step 3 — Judge the blockers
Not every unresolved issue blocks a release. Sort them:
| Kind | Ships without it? |
|---|---|
| Open defect, user-facing | No |
| Open defect, cosmetic | Usually yes — but say so and let the user decide |
| Unstarted feature work | Yes — move it to the next version |
| Blocked on something external | Depends; name what it is waiting on |
Use Issue.get with detail="full" on the open defects. Severity lives in the description, not the priority field, more often than people expect.
Step 4 — Draft release notes
If the version is ready or nearly so, draft the notes from what shipped:
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.
- 11d ago First seen · 106 lines · 94 tokens per session scan A 88fc4eea8977
release-checklist is a skill published in the GitHub repository Mr-pixle/jira-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 94 tokens to every session and 1,057 once invoked, about $0.0005 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
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
gsd-complete-milestone
Archive completed milestone and prepare for next version.
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.