Borrowing it
Nothing to install: this file belongs to erikdarlingdata/PerformanceMonitor. 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/erikdarlingdata/PerformanceMonitor/main/.claude/skills/release-checklist/SKILL.mdgit clone --depth 1 https://github.com/erikdarlingdata/PerformanceMonitorWrote 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/erikdarlingdata/performancemonitor/release-checklist)<a href="https://agentmods.dev/skills/erikdarlingdata/performancemonitor/release-checklist"><img src="https://agentmods.dev/badge/skills/erikdarlingdata/performancemonitor/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/erikdarlingdata/performancemonitor/release-checklist"><img src="https://agentmods.dev/badge/skills/erikdarlingdata/performancemonitor/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.00040 | $0.03675 |
| Opus 5 | $0.00020 | $0.01837 |
| Sonnet 5 | $0.00008 | $0.00735 |
| Haiku 4.5 | $0.00004 | $0.00367 |
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 2d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Release Checklist
Run through the full release prep checklist for PerformanceMonitor. $ARGUMENTS is the target version (e.g., 3.3.0).
Scope (since v3.3.0): the Full Dashboard and the CLI Installer are DEPRECATED and OUT of this process — they ship no release artifacts and get no live install/upgrade testing here. They still build and their test suites still run in CI on the release event, and they inherit the single
<Version>with everything else in the tree (below). The release artifacts are: Lite (zip + Velopack Setup.exe), the Darling service zip, and the Darling Viewer Setup.exe.
Checklist
Work through each step in order. Report status as you go. If a step fails, stop and report.
1. Version Bumps
Bump <Version> in Directory.Build.props. That is the whole step — one line, one file.
Every project in the tree inherits it, and AssemblyVersion / FileVersion / InformationalVersion derive
from it at build time. Do not add any of those four elements to a csproj: ProductVersionDeclarationTests
fails the build on a second <Version> property anywhere in the tree, on a re-added derived property, and
on a workflow or script that reads a version from any path but Directory.Build.props.
This replaced six independently hand-bumped csproj files (#3222). Two of them had been sitting three
releases behind, deprecated/Dashboard/Dashboard.csproj was declaring 3.6.0 while its binary stamped
3.3.0.0, and the release gate took its judgement from that file — so nothing in CI compared the version it
gated on against the version the artifacts were named with. Both now read the file above.
Verify no other files contain hardcoded version strings that need updating.
2. CHANGELOG
Ensure CHANGELOG.md has an entry for the new version with:
- Important section if there are store/schema changes or breaking changes (Darling store migrations, PG runtime upgrades with offline windows, operator actions required post-upgrade)
- Added section for new features
- Changed section for behavior changes
- Fixed section for bug fixes
- Reference links at the bottom for all issue numbers
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.
- 2d ago First seen · 183 lines · 40 tokens per session scan A b3bdf0dc792f
release-checklist is a skill published in the GitHub repository erikdarlingdata/PerformanceMonitor (494 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 3,675 once invoked, about $0.0002 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-10.
Other skills, from other repositories
operator-release
Finish feature PRs and cut Operator ETL software releases (CHANGELOG freeze, version bump, annotated tag). Use when merging ready PRs, shipping a version, or updating release process docs.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.