Borrowing it
Nothing to install: this file belongs to ivklgn/ai-kit. 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/ivklgn/ai-kit/main/.claude/skills/review-and-release/SKILL.mdgit clone --depth 1 https://github.com/ivklgn/ai-kitWrote 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/ivklgn/ai-kit/review-and-release)<a href="https://agentmods.dev/skills/ivklgn/ai-kit/review-and-release"><img src="https://agentmods.dev/badge/skills/ivklgn/ai-kit/review-and-release/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/ivklgn/ai-kit/review-and-release"><img src="https://agentmods.dev/badge/skills/ivklgn/ai-kit/review-and-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00061 | $0.01564 |
| Opus 5 | $0.00030 | $0.00782 |
| Sonnet 5 | $0.00012 | $0.00313 |
| Haiku 4.5 | $0.00006 | $0.00156 |
Grade A, and why
review-and-release 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 9d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review and Release
Synchronize README.md with the current set of agents and skills, validate files follow plugin conventions, sync the Codex plugin directory, bump the patch version in both plugin manifests, and create a release commit.
Step 1: Inventory Agents and Skills
Scan the filesystem to build the current state.
Agents:
ls agents/*.md
For each .md file, read the YAML frontmatter and extract name and description. Condense each description into a short README-style summary (under ~90 characters), matching the style of existing entries.
Skills:
ls skills/*/SKILL.md
For each SKILL.md, read the YAML frontmatter and extract name and description. Condense each description into a short README-style summary.
Store both inventories for use in subsequent steps.
Step 2: Diff Against README
Read README.md and parse its three inline lists (backtick-separated names, alphabetical):
## Agents—`name` · `name` · …## Skills— same format## Commands—`/ai-kit:name` · …(one entry percommands/*.mdfile)
Compare the filesystem inventory against README and classify:
- Added — in filesystem but not in the README list
- Removed — in the README list but not in filesystem
- Unchanged — matches
If zero differences across agents and skills, report "README is already in sync" and skip to Step 3.
Step 3: Validate Plugin Conventions
Check all agent and skill files against these rules:
Agent files (agents/*.md)
- Frontmatter present — starts with
---and has closing--- - Required fields —
name,description,tools,modelall present - Name matches filename —
namefield equals filename without.md - Model value — one of:
haiku,sonnet,opus,inherit - Description is non-empty
- Meaningful markdown body after frontmatter
Codex agent manifests (agents/*.toml)
Codex discovers subagents from .toml files, so every Claude Code agent must have a matching Codex manifest.
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.
- 9d ago First seen · 176 lines · 61 tokens per session scan A 35508eee52ab
review-and-release is a skill published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed 5d ago), licensed MIT. It adds 61 tokens to every session and 1,564 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
deploy-check
MUST use before any git push to main/master/production, or when user mentions 'deploy', 'going live', 'push to prod', 'ready to ship', 'merge to main', 'release'. Also trigger before any npm publish for CLI tools, or on 'audit', 'check vulnerabilities', 'are our deps safe?', 'npm audit', 'yarn audit'. Performs: test…
changelog
Generate a changelog from git history since a tag, date, or commit.
release-checklist
Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
team-release
Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…