What is release-analysis?

A process for examining an upstream release, such as a package, dependency, or platform update, and assessing what it means for the current repository.

Use it to inspect release notes or tags, identify breakage and redundancy, find new opportunities, and produce concrete recommendations for updates, tests, or no action.

Release notes alone do not show whether a change breaks local assumptions, replaces existing code, or creates maintenance work. This analysis connects the upstream changes to the repository that depends on them.

How chrysb/alphaclaw configures Claude Code and Codex

About the project

AlphaClaw is a browser-based management layer for OpenClaw, an AI-agent gateway, that guides setup and monitors running agents. It helps users configure multiple agents, manage integrations, recover gateway failures, and observe activity from one dashboard.

chrysb/alphaclaw · 1,479 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to chrysb/alphaclaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/chrysb/alphaclaw/main/.agents/skills/release-analysis/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/chrysb/alphaclaw

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/chrysb/alphaclaw/release-analysis/github.svg)](https://agentmods.dev/skills/chrysb/alphaclaw/release-analysis)

Your own site

<a href="https://agentmods.dev/skills/chrysb/alphaclaw/release-analysis"><img src="https://agentmods.dev/badge/skills/chrysb/alphaclaw/release-analysis/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/chrysb/alphaclaw/release-analysis"><img src="https://agentmods.dev/badge/skills/chrysb/alphaclaw/release-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 114 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,513 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00114	$0.01513
Opus 5.5	$0.00046	$0.00605
Sonnet 5.5	$0.00023	$0.00303
Haiku 4.5	$0.00011	$0.00151

Measured 2mo ago against content hash 2ac46f57c4a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-analysis 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 2mo 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.

.agents/skills/release-analysis/SKILL.md · 228 lines

How it starts

The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Analysis

Goal

Turn upstream release notes into a downstream product assessment:

What could break
What becomes redundant
What gets easier to support or expose
What should be updated, tested, or ignored

Default to a product-and-maintainer lens, not a changelog summary.

The user may provide only a package or repo name. In that case, resolve the upstream repository first, then inspect the latest release or tag notes before analyzing impact.

Workflow

Start from the package or repo name the user gave.
Resolve the canonical upstream repository.
Open the repository's latest stable release notes. If needed, use the tags page to find the newest relevant release/tag and read its notes.
Identify how this repo depends on or wraps that upstream project.
Separate automatic benefits from places where this repo has its own assumptions.
Look for regressions, redundancy, opportunity, and maintenance work.
End with concrete recommended actions.

Resolving The Repo

When the user provides only a package or repo name:

Prefer the canonical GitHub repository for that package.
If the package name is ambiguous, use package metadata, project docs, or the dependency declaration in this repo to confirm the source.
If multiple plausible repos exist and you cannot confidently resolve the right one, ask one short clarifying question before continuing.

Default to GitHub releases/tags as the source of truth for the analysis when available.

Find The Release Notes

Use this order:

Latest stable GitHub release page
Latest relevant tag page if the project publishes notes on tags
Release notes linked from the repository if GitHub has no usable notes

Prefer the latest stable release unless the user explicitly asks about beta, prerelease, or a specific version.

Gather Context

Read only what is needed:

The release notes or announcement from the latest release/tag
AGENTS.md and nearby project guidance
package.json or dependency pins
Version/update code paths
Any UI, route, or service files that expose the affected area
Tests covering the affected area, when the release looks risky

Read the full file on GitHub · 228 lines

Changes

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.

2mo ago First seen · 228 lines · 114 tokens per session scan A 2ac46f57c4a4

Subscribe to this mod's changes

release-analysis is a skill published in the GitHub repository chrysb/alphaclaw (1,479 stars, last pushed 14d ago), licensed MIT. It adds 114 tokens to every session and 1,513 once invoked, about $0.0005 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.

Git and workflow Releases ai-agent gateway nodejs openclaw setup-ui watchdog

release-analysis next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
release-analysischrysb/alphaclaw	Skill	1.5k	14d ago	MIT	A	114	Claude Code, Codex
draft-release-notesprisma/orm	Skill	48k	yesterday	Apache-2.0	A	174	Claude Code, Codex
publish-npm-versionprisma/orm	Skill	48k	yesterday	Apache-2.0	A	182	Claude Code, Codex
shipGCWing/BitFun	Skill	2.1k	2mo ago	MIT	A	105	Claude Code, Codex
installxiaotonng/pikiloom	Skill	293	4d ago	MIT	A	39	Claude Code, Codex
pm-releasekonglong87/superPM	Skill	86	11d ago	MIT	A	60	Claude Code
ensemble-releaseFortiumPartners/ensemble	Skill	12	yesterday	MIT	A	27	Claude Code, Codex

alphaclaw: Skill for Claude Code