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 skills add github/gh-aw --skill coordinator-response-modegit 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/coordinator-response-mode)<a href="https://agentmods.dev/skills/github/gh-aw/coordinator-response-mode"><img src="https://agentmods.dev/badge/skills/github/gh-aw/coordinator-response-mode.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.00079 | $0.01172 |
| Opus 5 | $0.00039 | $0.00586 |
| Sonnet 5 | $0.00016 | $0.00234 |
| Haiku 4.5 | $0.00008 | $0.00117 |
Grade A, and why
coordinator-response-mode 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 3d 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
2 near-identical copies found in the catalogue:
- coordinator-response-mode — 100% identical, 0 lines differ
- coordinator-response-mode — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load this skill when: you have routed work to an agent and need to pick the response mode (Direct / Lightweight / Standard / Full). The 1-line stub in
squad.agent.mdis for awareness; this skill is the full decision table + templates.
Response Mode Selection
After routing determines WHO handles work, select the response MODE based on task complexity. Bias toward upgrading — when uncertain, go one tier higher rather than risk under-serving.
| Mode | When | How | Target |
|---|---|---|---|
| Direct | Status checks, factual questions the coordinator already knows, simple answers from context | Coordinator answers directly — NO agent spawn | ~2-3s |
| Lightweight | Single-file edits, small fixes, follow-ups, simple scoped read-only queries | Spawn ONE agent with minimal prompt (see Lightweight Spawn Template below). Use agent_type: "explore" for read-only queries |
~8-12s |
| Standard | Normal tasks, single-agent work requiring full context | Spawn one agent with full ceremony — charter inline, history read, decisions read. This is the current default | ~25-35s |
| Full | Multi-agent work, complex tasks touching 3+ concerns, "Team" requests | Parallel fan-out, full ceremony, Scribe included | ~40-60s |
Direct Mode exemplars
Coordinator answers instantly, no spawn:
- "Where are we?" → Summarize current state from context: branch, recent work, what the team's been doing. A user favorite — make it instant.
- "How many tests do we have?" → Run a quick command, answer directly.
- "What branch are we on?" →
git branch --show-current, answer directly. - "Who's on the team?" → Answer from
team.mdalready in context. - "What did we decide about X?" → Answer from
decisions.mdalready in context.
Lightweight Mode exemplars
One agent, minimal prompt:
- "Fix the typo in README" → Spawn one agent, no charter, no history read.
- "Add a comment to line 42" → Small scoped edit, minimal context needed.
- "What does this function do?" →
agent_type: "explore"(Haiku model, fast). - Follow-up edits after a Standard/Full response — context is fresh, skip ceremony.
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.
- 3d ago First seen · 98 lines · 79 tokens per session scan A 9e022fe051a6
coordinator-response-mode is a skill published in the GitHub repository github/gh-aw (5,108 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 1,172 once invoked, about $0.0004 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.
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.