GitHub Agentic Workflows is a GitHub CLI extension that lets developers define AI-assisted repository automation in Markdown and run it through GitHub Actions. It is intended for tasks requiring interpretation or reasoning, such as issue triage, pull-request review, CI investigation, documentation maintenance, and dependency analysis. The catalogue entries provide skills and agents for working with these workflows.
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.
npx agentmods add skills/github/gh-aw/squad-version-checknpx skills add github/gh-aw --skill squad-version-checkgit clone --depth 1 https://github.com/github/gh-awWrote 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/github/gh-aw/squad-version-check)<a href="https://agentmods.dev/skills/github/gh-aw/squad-version-check"><img src="https://agentmods.dev/badge/skills/github/gh-aw/squad-version-check.svg" alt="Measured on agentmods" height="20"></a>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.00052 | $0.01706 |
| Opus 5 | $0.00026 | $0.00853 |
| Sonnet 5 | $0.00010 | $0.00341 |
| Haiku 4.5 | $0.00005 | $0.00171 |
Grade A, and why
squad-version-check 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 2d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- squad-version-check — 100% identical, 0 lines differ
- squad-version-check — 100% identical, 0 lines differ
- squad-version-check — 91% identical, 9 lines differ
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: Squad CLI Internals — Version Stamping & Upgrade Mechanics
Confidence: medium Discovered by: Data Date: 2026-05-26 Validated in: Issue #1173 recon (bradygaster/squad)
What This Skill Covers
Reusable knowledge about how @bradygaster/squad-cli stamps its version into squad.agent.md, how squad upgrade works, what it preserves vs. overwrites, and how to probe the npm registry for the latest version from a coordinator prompt.
Package & Registry Facts
- Package name:
@bradygaster/squad-cli - Registry: npm (public)
- CLI binary:
squad(registered viapackage.json#bin.squad) - Node version requirement: Node ≥22.5.0 (ESM-only codebase)
Version Stamping Mechanism
Source file: dist/cli/core/version.js
Three functions:
getPackageVersion()
Walks up from the compiled JS file to find package.json. Returns pkg.version. Works from both dist/cli/core/version.js and a bundled root cli.js. Returns '0.0.0' as fallback if not found.
stampVersion(filePath, version)
Mutates squad.agent.md in three places:
- HTML comment:
<!-- version: {version} -->(must be on the line immediately after frontmatter---) - Identity line:
- **Version:** {version} - Greeting instruction: backtick-quoted
`Squad v{version}`
Called by: both init and upgrade — after copying the template to the destination.
readInstalledVersion(filePath)
Reads the stamped version back from squad.agent.md:
- First tries HTML comment format:
/<!-- version: ([0-9.]+(?:-[a-z]+(?:\.\d+)?)?) -->/ - Falls back to old frontmatter format:
/^version:\s*"([^"]+)"/m - Returns
'0.0.0'on any error
squad upgrade Behavior
Source file: dist/cli/core/upgrade.js
What gets overwritten:
squad.agent.md— full overwrite from template, thenstampVersion()- Files with
overwriteOnUpgrade: trueinTEMPLATE_MANIFEST: casting JSON files, template .md files,copilot-instructions.md(if @copilot enabled) - GitHub Actions workflows — from
templates/workflows/; non-npm projects get type-aware stubs - Runs
runMigrations()after file copy
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.
- 2d ago First seen · 170 lines · 52 tokens per session scan A c533dd40c207
squad-version-check is a skill published in the GitHub repository github/gh-aw (5,104 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,706 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-09-03.
Other skills, from other repositories
watch-tag
Watch a GitHub repository for new tags using the gh-watch extension. Use when the user wants to be notified when a tag is created, when a release is cut, or when a tag that includes a specific commit appears (e.g. "tell me when my merge ships in a release").
AI Release Guardian
Analyze a git diff, map affected risks, select the tests that matter, detect coverage gaps on changed lines, run configurable quality gates, and produce a go/no-go release report with cited evidence. Recommends only; never merges or deploys.
release-habit-hooks
Cut a new release of the habit-hooks packages. Use when asked to release, publish, or bump the version. Reviews what lands, enforces the in-sync versioning rule, validates the changelog, and drives the tag-triggered PyPI publish.
publish-github-release
Use this whenever the user asks to ship, publish, release, tag, or cut a new version of the project — OR when CHANGELOG.md has an "Unreleased" / in-progress section ready to be shipped. The skill bumps the version across all version-bearing files, regenerates the CHANGELOG entry from git log since the last tag…
release-cut
Use this skill whenever Larry asks to cut a release (e.g., "prep vX.Y.Z release").
c-github
Interact with GitHub using the gh CLI and jq. Manage PRs, issues, repositories, and Actions workflows. Make raw API calls with gh api for anything not covered by built-in commands.