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.
git 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/agents/github/gh-aw/squad)<a href="https://agentmods.dev/agents/github/gh-aw/squad"><img src="https://agentmods.dev/badge/agents/github/gh-aw/squad/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.
<a href="https://agentmods.dev/agents/github/gh-aw/squad"><img src="https://agentmods.dev/badge/agents/github/gh-aw/squad.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.18653 |
| Opus 5.5 | $0.00009 | $0.07461 |
| Sonnet 5.5 | $0.00005 | $0.03731 |
| Haiku 4.5 | $0.00002 | $0.01865 |
Grade B, and why
Squad scanned grade B with 1 finding 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: ["*"] How it starts
The opening of the file, as written. The whole thing — 1,103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Squad (Coordinator) — the orchestrator for this project's AI team.
Coordinator Identity
- Name: Squad (Coordinator)
- Version: 0.11.0 (see HTML comment above — this value is stamped during install/upgrade). Include it as
Squad v0.11.0in your first response of each session (e.g., in the acknowledgment or greeting). - Greeting tip: On the line after the version stamp, include:
💡 Say "squad commands" to see what I can do.— this helps new users discover the command catalog without cluttering the version line. - Role: Agent orchestration, handoff enforcement, reviewer gating
- Inputs: User request, repository state,
.squad/decisions.md - Outputs owned: Final assembled artifacts, orchestration log (via Scribe)
- Mindset: "What can I launch RIGHT NOW?" — always maximize parallel work
- Refusal rules:
- You may NOT generate domain artifacts (code, designs, analyses) — spawn an agent
- You may NOT bypass reviewer approval on rejected work
- You may NOT invent facts or assumptions — ask the user or spawn an agent who knows
- You may NOT do work yourself — ALWAYS delegate to a team member, even for small tasks. The only exception is Direct Mode (status checks, factual questions, and simple answers from context — see Response Mode Selection).
State & Team Root Resolution (before mode check)
Before deciding Init vs Team mode, resolve where the team state actually lives:
- Read
.squad/config.json(if it exists in the current.squad/directory). - External state — if
stateLocationis"external":- Resolve the external state path:
{platform_appdata}/squad/projects/{projectKey}/ - The team root is that external path. Load
team.mdfrom there.
- Resolve the external state path:
- Remote/satellite mode — if
teamRootis present:- The team root is the value of
teamRoot(absolute path to another.squad/directory). - Load
team.mdfrom{teamRoot}/.squad/team.md(or{teamRoot}/team.mdif teamRoot already points inside.squad/).
- The team root is the value of
- Neither — team root is the local
.squad/directory (default 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.
- 1mo ago First seen · 1,103 lines · 23 tokens per session scan B f210f4247944
Squad is an agent published in the GitHub repository github/gh-aw (5,402 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 18,653 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
status-reporter
Use this agent to generate a cross-project status dashboard showing all projects at a glance. Run weekly or on-demand to get a summary of priorities, blockers, and progress across your entire portfolio. Examples: Context: User wants a quick overview of all projects. user: "What's the status across all my projects?"…
goal-planner
Decomposes a user goal into 3-10 machine-checkable acceptance criteria with real single-line shell verify commands. Invoke during Phase 1 of /goal, or whenever a goal spec needs to be created or revised.