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/agent-collaborationnpx skills add github/gh-aw --skill agent-collaborationgit 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/agent-collaboration)<a href="https://agentmods.dev/skills/github/gh-aw/agent-collaboration"><img src="https://agentmods.dev/badge/skills/github/gh-aw/agent-collaboration.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 | $0.00022 | $0.00440 |
| Opus 5 | $0.00011 | $0.00220 |
| Sonnet 5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
agent-collaboration 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 yesterday.
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
8 near-identical copies found in the catalogue:
- agent-collaboration — 100% identical, 0 lines differ
- agent-collaboration — 100% identical, 0 lines differ
- agent-collaboration — 100% identical, 0 lines differ
- agent-collaboration — 100% identical, 0 lines differ
- agent-collaboration — 100% identical, 0 lines differ
- agent-collaboration — 100% identical, 0 lines differ
- agent-collaboration — 100% identical, 84 lines differ
- agent-collaboration — 100% identical, 0 lines differ
What it actually says
Context
Every agent on the team follows identical collaboration patterns for worktree awareness, decision recording, and cross-agent communication. These were previously duplicated in every charter's Collaboration section (~300 bytes × 18 agents = ~5.4KB of redundant context). Now centralized here.
The coordinator's spawn prompt already instructs agents to read decisions.md and their history.md. This skill adds the patterns for WRITING decisions and requesting help.
Patterns
Worktree Awareness
Use the TEAM ROOT path provided in your spawn prompt. All .squad/ paths are relative to this root. If TEAM ROOT is not provided (rare), run git rev-parse --show-toplevel as fallback. Never assume CWD is the repo root.
Decision Recording
After making a decision that affects other team members, write it to:
.squad/decisions/inbox/{your-name}-{brief-slug}.md
Format:
### {date}: {decision title}
**By:** {Your Name}
**What:** {the decision}
**Why:** {rationale}
Cross-Agent Communication
If you need another team member's input, say so in your response. The coordinator will bring them in. Don't try to do work outside your domain.
Reviewer Protocol
If you have reviewer authority and reject work: the original author is locked out from revising that artifact. A different agent must own the revision. State who should revise in your rejection response.
Anti-Patterns
- Don't read all agent charters — you only need your own context + decisions.md
- Don't write directly to
.squad/decisions.md— always use the inbox drop-box - Don't modify other agents' history.md files — that's Scribe's job
- Don't assume CWD is the repo root — always use TEAM ROOT
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.
- yesterday First seen · 43 lines · 22 tokens per session scan A e1943766f6aa
agent-collaboration is a skill published in the GitHub repository github/gh-aw (5,091 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 440 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-09-03.
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.
suivi-actions
Extraire et suivre les actions et décisions ouvertes à travers les comptes-rendus.
Apple Reminders
Create, organize, and manage reminder lists for personal tasks.
Google Calendar
Schedule meetings, focused work blocks, and calendar events without conflicts.
helix-iscompleted-bucketing
Completion-safe bucketing for Helix work items with nullable exit codes.
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.