A command that upgrades the GitHub Agentic Workflows extension, recompiles and checks repository workflows, and can create a pull request. A pull request is a proposed set of changes for review before merging.

Use it to roll out gh-aw upgrades, validate all affected workflows, and prepare pull requests for review or merging.

It gathers the upgrade, validation, and review steps into one repeatable process across repositories. Dry-run, strict-validation, and no-merge options control how much it changes.

aw-upgrade — Command for Claude Code by zircote-plugins

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.

Clone the repo

git clone --depth 1 https://github.com/zircote-plugins/github-agentic-workflows

Made for: Claude Code.

Or install aw-author, the plugin that ships this one along with the rest of its 3 skills, 6 commands, 1 agent.

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/commands/zircote-plugins/github-agentic-workflows/aw-upgrade/github.svg)](https://agentmods.dev/commands/zircote-plugins/github-agentic-workflows/aw-upgrade)

Your own site

<a href="https://agentmods.dev/commands/zircote-plugins/github-agentic-workflows/aw-upgrade"><img src="https://agentmods.dev/badge/commands/zircote-plugins/github-agentic-workflows/aw-upgrade/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/commands/zircote-plugins/github-agentic-workflows/aw-upgrade"><img src="https://agentmods.dev/badge/commands/zircote-plugins/github-agentic-workflows/aw-upgrade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,704 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.

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.00018	$0.02704
Opus 5.5	$0.00007	$0.01082
Sonnet 5.5	$0.00004	$0.00541
Haiku 4.5	$0.00002	$0.00270

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

Security

Grade A, and why

aw-upgrade 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 1mo 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.

commands/aw-upgrade.md · 301 lines

How it starts

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

/aw-upgrade

End-to-end gh-aw upgrade, recompile, validate, and PR cycle. Designed for idempotent, unattended execution across many repos.

Usage

/aw-upgrade                → Full upgrade cycle: upgrade extension → upgrade repo → validate → PR → merge
/aw-upgrade --force        → Run even if gh-aw extension is already on latest version
/aw-upgrade --dry-run      → Show what would change without committing or creating a PR
/aw-upgrade --no-merge     → Create PR but do not auto-merge
/aw-upgrade --strict       → Enforce strict mode validation for all workflows

Workflow

You are an operations automation agent performing an unattended gh-aw upgrade cycle. Execute the phases below in order. If any phase fails, stop immediately, report which phase failed and why, and do not proceed to subsequent phases.

Do not prompt the user for input at any point. This command is designed for bulk execution ($GPM_PROVISION_BULK=true).

Parse the argument string for flags: --force, --dry-run, --no-merge, --strict. Unknown flags should be rejected with an error message.

Phase 1: Pre-flight checks

Verify gh CLI is available: gh --version
Verify gh aw extension is installed: gh aw version
- If not installed, install it: gh extension install github/gh-aw
- After install, capture version: gh aw version
Verify the current directory is a git repository with .github/workflows/ containing at least one .md file
Verify working tree is clean: git status --porcelain must be empty
- If not clean, abort with error: "Working tree is dirty. Commit or stash changes before running /aw-upgrade."
Capture the current branch name for later restoration

Report: current gh-aw version, repo name, number of .md workflow files found.

Phase 2: Upgrade gh-aw extension

Record the before version: gh aw version
Run: gh extension upgrade github/gh-aw --force
Record the after version: gh aw version
Compare versions:
- If versions are identical and --force was NOT passed: report "gh-aw is already on latest version (vX.Y.Z). No upgrade needed." and exit successfully (skip all remaining phases).
- If versions are identical and --force WAS passed: continue to Phase 3 with note "Forced recompile on same version."
- If versions differ: report "Upgraded gh-aw from vX.Y.Z to vA.B.C" and continue.

Read the full file on GitHub · 301 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.

1mo ago First seen · 301 lines · 18 tokens per session scan A efeab8612a7b

Subscribe to this mod's changes

aw-upgrade is a command published in the GitHub repository zircote-plugins/github-agentic-workflows (2 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 2,704 once invoked, about $0.0001 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-31.

Claude Code Git and workflow Releases agentic-ai ai-tools claude-code-plugin developer-tools github-actions

aw-upgrade

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/aw-upgrade

Usage

Workflow

Phase 1: Pre-flight checks

Phase 2: Upgrade gh-aw extension

What this file has done since we first saw it

Other commands, from other repositories

ia-document-release

ia-changelog

release

release

repo-sprint

repo-week