agentmods.dev

release-status

release-status is a skill for Claude Code from flurdy/agent-skills. It costs 56 tokens per session (2,155 once invoked), scanned A, original, MIT.

A read-only dashboard for showing what can be proved about a project's release state. A release is the process of getting code from development into production; the dashboard covers pending pushes, CI, deployment progress, ordering blockers, and optional feature toggles.

In plain words
What is it for?
Use it to check the release situation across services or inspect one service before starting a release-watch or release-management workflow.
Why use it?
It gives a quick release snapshot without prompting, pushing code, or changing project state. It reports only information supported by the project's release digest.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

not rated 8 +1 7d ago A scan 56 tokens original MIT
View the source file flurdy/agent-skills
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/flurdy/agent-skills/release-status
Any agent
npx skills add flurdy/agent-skills --skill release-status
Clone the repo
git clone --depth 1 https://github.com/flurdy/agent-skills

Made for: Claude Code.

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.

agentmods badge for release-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/flurdy/agent-skills/release-status.svg)](https://agentmods.dev/skills/flurdy/agent-skills/release-status)
Your own site
<a href="https://agentmods.dev/skills/flurdy/agent-skills/release-status"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/release-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,155 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.02155
Opus 5 $0.00028 $0.01077
Sonnet 5 $0.00011 $0.00431
Haiku 4.5 $0.00006 $0.00215

Measured 5d ago against content hash 910dcb8af42b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

release-status 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 5d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (tests/test-skill-contract.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/release-status/SKILL.md · 161 lines

How it starts

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

Release Status

A read-only snapshot of release state across a project's services. It is the passive sibling of /release-manager: show only states supported by available project evidence, take no action, and ask no questions.

When to Use

  • A quick "what's the release situation right now" glance
  • Before starting /watch-release, to see the baseline
  • To inspect what /release-manager could evaluate without being prompted

For the interactive gatekeeper, use /release-manager. For a deep gate on one service, use /ready-to-release <service>.

Usage

/release-status                 # all services
/release-status dispatch        # one service

Instructions

  1. Gather the project digest. Run the shared mechanical digest and pass through any service argument:

    ./scripts/release-digest

    The digest is the required project adapter. If it is missing, exits nonzero, omits the service header, or is malformed, print one bounded _Release status unavailable: <reason>_ line and stop. Do not guess from project files or invoke a provider directly.

    Parse its ANSI-free sections:

    • ---META---: context=<name>, ciProvider=<circleci|github-actions|cloud-build|none>, and ci=<available|partial|unavailable>. Provider identity is diagnostic only; decision and rendering logic use normalized fields below and never branch by provider.
    • ---SERVICES---: one pipe-delimited row per service after this exact header: service|unpushed|uncommitted|ci|ciBranch|gitBranch|head|deploy|tag|age|ciRevision|ciExpectedRevision.
      • unpushed is commits ahead of upstream; uncommitted is true|false; head is local HEAD.
      • ci is success|failed|running|error|unknown. Treat it as unknown for display when ciBranch != gitBranch, either revision is -, or ciRevision != ciExpectedRevision. A provider's branch-only or stale green is not exact evidence.
      • deploy, tag, and age are optional deployment observations. An N/M value and cron/cron:rollout are observable; unknown, notfound, not-applicable, and - are not evidence of deployment state.
    • ---TOGGLES---: optional FLAG=value lines. Use them only when the optional manifest context in step 2 declares toggle policy.

Read the full file on GitHub · 161 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 5d ago First seen · 161 lines · 56 tokens per session scan A 910dcb8af42b

Subscribe to this mod's changes

release-status is a skill published in the GitHub repository flurdy/agent-skills (8 stars, last pushed 7d ago), licensed MIT. It adds 56 tokens to every session and 2,155 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-31.

DevOps and cloudGit and workflowReleasesagent-skillsclaudecodex
Related

Other skills, from other repositories

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.

paperclipai/paperclip · 42 tokens

agent-release-swarm

Agent skill for release-swarm - invoke with $agent-release-swarm.

ruvnet/ruflo · 19 tokens

release

Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.

openai/symphony · 42 tokens

changelog

Create changelog files for important commits in a PR.

pipecat-ai/pipecat · 13 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

refresh-arm-sdk-release

WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…

Azure/azure-sdk-for-net · 91 tokens