Borrowing it
Nothing to install: this file belongs to prove-ai/agentpulse. 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/prove-ai/agentpulse/main/.claude/skills/release-regression-check/SKILL.mdgit clone --depth 1 https://github.com/prove-ai/agentpulseWrote 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/prove-ai/agentpulse/release-regression-check)<a href="https://agentmods.dev/skills/prove-ai/agentpulse/release-regression-check"><img src="https://agentmods.dev/badge/skills/prove-ai/agentpulse/release-regression-check.svg" alt="Measured on agentmods" 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.00054 | $0.00310 |
| Opus 5 | $0.00027 | $0.00155 |
| Sonnet 5 | $0.00011 | $0.00062 |
| Haiku 4.5 | $0.00005 | $0.00031 |
Grade A, and why
release-regression-check 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 8d 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.
What it actually says
Release regression check
Answer "did this release regress?" and attribute the drift to the release that caused it.
Steps
- Call
get_version_comparison:- No versions named → default (baseline → newest).
- Two named (e.g. "v3 vs v4") →
base_version+target_version. - "which release broke it" / "across all versions" →
across_all=True.
- Lead with the critical drift, stating which version introduced it (
introduced_in). - Report the metrics that changed for that root and the outcome it broke (e.g. clean-finish rate).
- Only mention intended changes if asked (
include_intended=True) — label them intended, not regressions. Hide low-confidence unless asked (include_low_confidence=True). - If a critical drift is found, offer
get_next_check_steps.
Principles
- Always state which two versions were compared.
- "Baseline vs newest" spans multiple releases — attribute to the release that introduced the drift, not the whole span.
- A metric moving ≠ a regression. Only outcome-breaking, high-confidence drift is critical.
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.
- 8d ago First seen · 24 lines · 54 tokens per session scan A 4c05133ba85b
release-regression-check is a skill published in the GitHub repository prove-ai/agentpulse (11 stars, last pushed 3d ago), licensed MIT. It adds 54 tokens to every session and 310 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
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
verify-and-ship
Run all quality checks (tests, lint, typecheck), fix failures, update the changelog, commit, push, and create/update the pull request or merge request.
ship-workflow
Automated release pipeline: merges main, runs tests, pre-landing review, version bump, changelog, bisectable commits, and PR creation. Triggers on: "ship it", "release this", "prepare for release", "open a PR", "push and PR", "land this", "/ship-workflow".
AI Release Guardian
Analyze a git diff, map affected risks, select the tests that matter, detect coverage gaps on changed lines, run configurable quality gates, and produce a go/no-go release report with cited evidence. Recommends only; never merges or deploys.
repo-harness-check
Verification entrypoint for repo-harness workflow readiness. Runs workflow gates, task sync, contract checks, inspector, and migration dry-run before merge or release.
mathodology-dev-test-release
Use when checking skill metadata, references or repository boundaries, or preparing an explicitly requested skills release.