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/awf-release-integratornpx skills add github/gh-aw --skill awf-release-integratorgit clone --depth 1 https://github.com/github/gh-awWhat 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 | $0.00023 | $0.00838 |
| Opus 5 | $0.00012 | $0.00419 |
| Sonnet 5 | $0.00005 | $0.00168 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
awf-release-integrator 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWF Release Integrator
Use this skill when updating github/gh-aw to a newer github/gh-aw-firewall release.
Goal
Land the version bump cleanly, rebuild the generated artifacts, and review upstream release/spec changes for any follow-up work that should accompany the bump.
Required sources
Consult these sources before editing anything:
- The latest
github/gh-aw-firewallrelease metadata and body. - The current gh-aw version pins in
pkg/constants/version_constants.go. - The canonical AWF config sources spec in
specs/awf-config-sources-spec.md. - The embedded AWF schema in
pkg/workflow/schemas/awf-config.schema.json. - AWF config integration code in:
pkg/workflow/awf_config.gopkg/workflow/awf_config_build.gopkg/workflow/awf_config_schema.gopkg/workflow/awf_config_policy.gopkg/workflow/awf_helpers.go- related AWF tests under
pkg/workflow/
For upstream spec review, compare these files from the target github/gh-aw-firewall release or tag:
docs/awf-config-spec.mddocs/awf-config.schema.jsonsrc/awf-config-schema.json- any release assets such as
awf-config.schema.json
Update procedure
- Read
pkg/constants/version_constants.goand record:DefaultFirewallVersion- every
AWF*MinVersionconstant
- Look up the latest
github/gh-aw-firewallrelease. - If the latest release tag matches
DefaultFirewallVersion, report that no version bump is needed and only continue with spec/release-note review if explicitly requested. - If a newer release exists, update the gh-aw pins:
- bump
DefaultFirewallVersion - update any
AWF*MinVersionconstants that must move because the new release introduces or changes gated flags/features
- bump
- Review release notes for:
- new flags
- removed or deprecated flags
- schema/config additions
- security fixes
- behavioral changes that could require new tests, docs, or ADR/spec updates
- Review the upstream AWF specification and schema changes against:
pkg/workflow/schemas/awf-config.schema.jsonspecs/awf-config-sources-spec.md- local AWF config generation and validation code
- Update any directly related gh-aw files needed for a complete integration, such as:
- embedded schema copies
- version-gated helpers/tests
- specs or ADRs documenting newly surfaced AWF behavior
- Add or update a patch changeset when the bump changes shipped behavior.
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 · 95 lines · 23 tokens per session scan A bc3b20575bbc
awf-release-integrator is a skill published in the GitHub repository github/gh-aw (5,084 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 838 once invoked, about $0.0001 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
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.
watch-pr
Watch a GitHub pull request for CI status, reviews, comments, merge conflicts, and terminal states using the gh-watch extension. Use when the user wants to monitor a PR, wait for CI, or track PR progress.
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").
watch-branch
Watch a GitHub branch for new commits using the gh-watch extension. Use when the user wants to be notified when new commits are pushed to a branch, monitor main for merges, or track branch activity.
watch-commit
Watch a GitHub commit for CI status changes using the gh-watch extension. Use when the user wants to monitor a commit's CI checks, wait for a build to finish, or track CI progress on a specific SHA.
update-architecture-docs
Generate or update the architecture documentation in docs/content/architecture/. Use on "update architecture docs", "generate architecture documentation", "regenerate architecture docs", or after any structural change to the codebase.