Agent skill

Release Watch

by alpha-omega-security in alpha-omega-security/scrutineer

After a finding has been marked fixed, watch the upstream for a release that contains the fix.

MITAuto-check passedSecurity

Install Release Watch

skills CLI

$ npx skills add alpha-omega-security/scrutineer --skill release-watch -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install alpha-omega-security/scrutineer release-watch --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/release-watch .claude/skills/release-watch && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "release-watch" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/release-watch into .claude/skills/release-watch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-watch", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/alpha-omega-security/scrutineer/tree/main/skills/release-watch

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add alpha-omega-security/scrutineer --skill release-watch -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install alpha-omega-security/scrutineer release-watch --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/release-watch .agents/skills/release-watch && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "release-watch" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/release-watch into .agents/skills/release-watch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-watch", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add alpha-omega-security/scrutineer --skill release-watch -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install alpha-omega-security/scrutineer release-watch --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/release-watch .cursor/skills/release-watch && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "release-watch" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/release-watch into .cursor/skills/release-watch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-watch", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/alpha-omega-security/scrutineer.git --path skills/release-watch

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add alpha-omega-security/scrutineer --skill release-watch -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install alpha-omega-security/scrutineer release-watch --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/release-watch .gemini/skills/release-watch && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "release-watch" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/release-watch into .gemini/skills/release-watch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-watch", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install alpha-omega-security/scrutineer release-watch

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add alpha-omega-security/scrutineer --skill release-watch -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/release-watch .github/skills/release-watch && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "release-watch" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/release-watch into .github/skills/release-watch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-watch", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add alpha-omega-security/scrutineer --skill release-watch -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install alpha-omega-security/scrutineer release-watch --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/alpha-omega-security/scrutineer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/release-watch .opencode/skills/release-watch && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "release-watch" agent skill from https://github.com/alpha-omega-security/scrutineer/tree/main/skills/release-watch into .opencode/skills/release-watch/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-watch", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: release-watch
GitHub stars: 239
Token cost: ~1.3k tokens
SKILL.md length: 529 words
Files: 2
Skills in repo: 48
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

After a finding has been marked fixed, watch the upstream for a release that contains the fix.

Works in 3 steps: Fetch the finding → List releases on the upstream. On… → Map each release back to a commit. For…
Security work in your project
SKILL.md covers Workspace, Inputs and Procedure
Calls gh; reaches github.com

What it does

Release Watch is an agent skill from alpha-omega-security/scrutineer. After a finding has been marked fixed, watch the upstream for a release that contains the fix. When one shows up, record the release tag, URL, and timestamp on the finding. Closes the gap between "the maintainer landed a patch" and "consumers have a shipped version they can pin to".

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `schema.json`). Compatibility notes: Needs network access to the scrutineer skill API and to github.com (or whichever host the upstream lives on). Read-only.

It sits in Security. The repository describes itself as: Security through scrutiny. The licence is MIT.

When your agent uses it

Security work in your project

Example prompts

“the maintainer landed a patch”
“consumers have a shipped version they can pin to”
“/release-watch”

Requirements

Compatibility (from SKILL.md): Needs network access to the scrutineer skill API and to github.com (or whichever host the upstream lives on). Read-only.

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Fetch the finding
List releases on the upstream. On github.com
Map each release back to a commit. For each release whose target_commitish is empty (sometimes tags are detached), resolve via

What it can do on your machine

Read from SKILL.md and the folder at commit f3407bf. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Needs network access to the scrutineer skill API and to github.com (or whichever host the upstream lives on). Read-only.
From compatibility in the SKILL.md frontmatter.

Context cost

Release Watch loads about 1.3k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 529 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~74
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from alpha-omega-security/scrutineer at commit f3407bf, republished under its MIT licence (© alpha-omega-security). 529 words, ~1,255 tokens.

Download SKILL.mdSave it as .claude/skills/release-watch/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: release-watch
description: After a finding has been marked fixed, watch the upstream for a release that contains the fix. When one shows up, record the release tag, URL, and timestamp on the finding. Closes the gap between "the maintainer landed a patch" and "consumers have a shipped version they can pin to".
compatibility: Needs network access to the scrutineer skill API and to github.com (or whichever host the upstream lives on). Read-only.
license: MIT
metadata.scrutineer.version: 1
metadata.scrutineer.output_file: report.json
metadata.scrutineer.output_kind: release_watch
metadata.scrutineer.requires_remote: true
metadata.scrutineer.model: mid

release-watch

A finding reached fixed because a commit landed upstream. Consumers cannot pin to a commit; they need a tagged release. This skill answers "did the maintainer cut one yet, and what's the version".

The skill is finding-scoped. Run it after the finding has been marked fixed (the triage skill auto-enqueues this for every fixed finding on each repo run). When no release has shipped yet, the answer is just that — return released: false and a short note about what the latest release looks like. The next run will check again.

Workspace

./src — the upstream repository at the scanned commit
./context.json — has scrutineer.api_base, scrutineer.token, scrutineer.finding_id, scrutineer.repository_id, and repository.url / repository.full_name
./report.json — write your finding here
./schema.json — output shape

Inputs

Fetch the finding:
```
GET {api_base}/findings/{finding_id}
Authorization: Bearer {token}
```
Read fix_commit, fix_version, status, and the existing released_at / release_tag / release_url on the finding. If a release is already recorded, write {"released": true, "release_tag": "<existing tag>", ..., "notes": "already recorded; re-confirming"} and exit — re-runs should not flap a recorded value.

If status is not fixed, write {"released": false, "notes": "skill only meaningful in fixed status; finding is in <status>"} and exit.
List releases on the upstream. On github.com:
```
gh api repos/{owner}/{repo}/releases?per_page=20
```
The response gives you tag_name, name, html_url, published_at, and target_commitish. If gh auth fails, write {"released": false, "notes": "gh auth not configured; cannot list releases"} and exit.

Non-GitHub hosts: skip for now and record a note. A later iteration covers GitLab, gitea, and registry-only sources.
Map each release back to a commit. For each release whose target_commitish is empty (sometimes tags are detached), resolve via:
```
gh api repos/{owner}/{repo}/git/ref/tags/{tag_name}
```
to get the tag's SHA, then gh api repos/{owner}/{repo}/commits/{sha} to confirm. Skip a release if its commit cannot be resolved; do not guess.

Show full SKILL.md (286 more words)Show less

Procedure

Match by commit. When the finding has a fix_commit, check each release for whether fix_commit is reachable from the release's commit. Use:
```
gh api repos/{owner}/{repo}/compare/{fix_commit}...{release_commit}
```
If the comparison succeeds with status: ahead or identical (the release commit is at or after the fix commit), this release contains the fix. Pick the earliest such release by published_at: consumers want the first version they can upgrade to.
Fall back to fix_version. If fix_commit is empty but fix_version is set, match by tag name: a release whose tag_name matches fix_version (with or without a leading v) is the one. Verify by fetching its commit, just so you have the timestamp.
Neither field set. Write {"released": false, "notes": "finding has no fix_commit or fix_version to anchor the search"} and exit. This is a recoverable state: the analyst can fill in either field and re-run.
A release was found. Emit:
json
```
{
  "released": true,
  "release_tag": "v2.3.1",
  "release_url": "https://github.com/example/lib/releases/tag/v2.3.1",
  "release_at": "2026-06-02T14:00:00Z",
  "notes": "matched by fix_commit; release contains 4 commits since the fix"
}
```
released_at is ISO 8601. Scrutineer writes it to Finding.ReleasedAt and the rest to the matching columns, with the change recorded in finding history. It also adds a FindingReference row with tags=upstream-release so the release link appears in the finding's references panel.
No matching release yet. Emit:
json
```
{
  "released": false,
  "notes": "latest release v2.3.0 from 2026-05-30 predates fix_commit abc1234"
}
```
The next run rechecks. Make the note specific enough that a human can tell if the maintainer is sitting on the fix.

Do not transition the finding's lifecycle status. published means the advisory has been published, which is a human act and a different signal from a release shipping; release-watch records the release but leaves status alone.

Files

SKILL.md and 1 other file in skills/release-watch of alpha-omega-security/scrutineer.

SKILL.md
schema.json

Open the folder on GitHubat commit f3407bf

Compare with similar skills

Release Watch next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release Watch compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Release Watch this skillalpha-omega-security/scrutineer	239	—	~1.3k	Automated safety check: Pass	MIT	today
Fla Ascend Performancefla-org/flash-linear-attention	5.8k	—	~6.3k	Automated safety check: Pass	MIT	today
Deepsec Documentation Guidevercel-labs/deepsec	8.1k	—	~956	Automated safety check: Pass	Apache-2.0	10 days ago
Skill Scannergetsentry/skills	1k	4 repos	~2.5k	Automated safety check: Warn	Apache-2.0	6 days ago
Serenity Aleabitoreddityan-labs/serenity-aleabitoreddit	481	1 repos	~3.3k	Automated safety check: Pass	None	8 days ago
Security Alert Triageelastic/agent-skills	592	1 repos	~3.5k	Automated safety check: Notes	Apache-2.0	yesterday

Similar skills

Fla Ascend Performance
fla-org/flash-linear-attention
Guidelines for Ascend NPU kernel / Triton-Ascend backend performance work in the FLA repo.
5.8k GitHub stars~6.3k tokensUpdated today
SecurityAuto-check passed
Deepsec Documentation Guide
vercel-labs/deepsec
Official
Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.
8.1k GitHub stars~956 tokensUpdated 10 days ago
SecurityAuto-check passed
Skill Scanner
getsentry/skills
Official
Scan agent skills for security issues. An agent skill from getsentry/skills.
1k GitHub starsUsed in 4 repos~2.5k tokens
SecurityAuto-check: warnings
Serenity Aleabitoreddit
yan-labs/serenity-aleabitoreddit
Apply trader Serenity's (@aleabitoreddit) AI/semiconductor supply-chain analytical lens to US-stock ideas and market judgment.
481 GitHub starsUsed in 1 repo~3.3k tokens
SecurityAuto-check passed
Security Alert Triage
elastic/agent-skills
Official
Triage Elastic Security alerts — gather context, classify threats, create cases, and acknowledge.
592 GitHub starsUsed in 1 repo~3.5k tokens
SecurityAuto-check: notes
Shiro Attack CLI
SummerSec/ShiroAttack2
当用户要求利用、检测或测试 Apache Shiro rememberMe 反序列化漏洞 (Shiro-550, CVE-2016-4437) 时使用。触发词包括 "Shiro"、"rememberMe"、"shiro attack"、"CVE-2016-4437"、"Shiro-550"、"爆破 Shiro key"、"利用 Shiro"、"Shiro…
2.6k GitHub stars~945 tokensUpdated 4 mo ago
SecurityAuto-check passed

More from alpha-omega-security/scrutineer

All 48 skills in this repo

Triage
alpha-omega-security/scrutineer
Default pipeline scrutineer runs when a repository is added.
239 GitHub stars~2.9k tokensUpdated today
Auto-check passed
Zizmor
alpha-omega-security/scrutineer
Audit GitHub Actions workflows with zizmor and explain reported hits using bundled trust-boundary references.
239 GitHub stars~1.2k tokensUpdated today
Auto-check passed
Bandit
alpha-omega-security/scrutineer
Run bandit against the Python source in the repository and map its hits into the findings shape.
239 GitHub stars~615 tokensUpdated today
Auto-check: notes
Compliance
alpha-omega-security/scrutineer
Audit the repository against the OpenSSF Baseline with darnit, resolve the controls darnit defers to LLM analysis or could not verify, and record per-control verdicts plus the attained Baseline level.
239 GitHub stars~1.4k tokensUpdated today
Auto-check: notes
Dependencies
alpha-omega-security/scrutineer
Run git-pkgs list and sbom against the repository and emit one envelope with per-section status.
239 GitHub stars~596 tokensUpdated today
Auto-check passed
History
alpha-omega-security/scrutineer
Mine repository history for security fixes that were never published as advisories, producing a cached worklist for threat-model and advisory-deep-dive.
239 GitHub stars~2.9k tokensUpdated today
Auto-check: notes

Questions about Release Watch

What does Release Watch do?

After a finding has been marked fixed, watch the upstream for a release that contains the fix. Release Watch is an agent skill from alpha-omega-security/scrutineer. After a finding has been marked fixed, watch the upstream for a release that contains the fix.

When should I use Release Watch?

Release Watch fits situations like: security work in your project.

How do I install Release Watch in Claude Code?

Run `npx skills add alpha-omega-security/scrutineer --skill release-watch -a claude-code`. Or copy the skill folder (skills/release-watch in alpha-omega-security/scrutineer) into .claude/skills/release-watch in your project. Claude Code loads it when a task matches its description.

How do I install Release Watch in Codex?

Run `npx skills add alpha-omega-security/scrutineer --skill release-watch -a codex`. Or copy the skill folder (skills/release-watch in alpha-omega-security/scrutineer) into .agents/skills/release-watch in your project. Codex loads it when a task matches its description.

Can I use Release Watch in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alpha-omega-security/scrutineer --skill release-watch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-watch, .gemini/skills/release-watch, .github/skills/release-watch and .opencode/skills/release-watch in your project.

What does Release Watch need to run?

Going by SKILL.md and its folder, Release Watch needs the command-line tools its instructions call (gh). Compatibility (from SKILL.md): Needs network access to the scrutineer skill API and to github.com (or whichever host the upstream lives on). Read-only..

Does Release Watch access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Release Watch safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Release Watch use?

Release Watch is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release Watch use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release Watch?

Skills that share tags, products or a category with Release Watch: Fla Ascend Performance (fla-org/flash-linear-attention, 5.8k stars), Deepsec Documentation Guide (vercel-labs/deepsec, 8.1k stars), Skill Scanner (getsentry/skills, 1k stars) and Serenity Aleabitoreddit (yan-labs/serenity-aleabitoreddit, 481 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Watch?

alpha-omega-security (a GitHub organization) maintains it in alpha-omega-security/scrutineer, which has 239 GitHub stars. The repository holds 48 skills in this directory. The repository was last updated on October 9, 2026.

Source: alpha-omega-security/scrutineer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Release Watch

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

release-watch

Workspace

Inputs

Procedure

Files

Compare with similar skills

Similar skills

More from alpha-omega-security/scrutineer

Related

Questions about Release Watch