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/personal-squadnpx skills add github/gh-aw --skill personal-squadgit 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/personal-squad)<a href="https://agentmods.dev/skills/github/gh-aw/personal-squad"><img src="https://agentmods.dev/badge/skills/github/gh-aw/personal-squad.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.00014 | $0.00515 |
| Opus 5 | $0.00007 | $0.00258 |
| Sonnet 5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
personal-squad 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:
- personal-squad — 100% identical, 0 lines differ
- personal-squad — 100% identical, 0 lines differ
- personal-squad — 95% identical, 13 lines differ
- personal-squad — 95% identical, 13 lines differ
- personal-squad — 95% identical, 13 lines differ
- personal-squad — 95% identical, 123 lines differ
- personal-squad — 95% identical, 13 lines differ
- personal-squad — 95% identical, 13 lines differ
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Personal Squad — Skill Document
What is a Personal Squad?
A personal squad is a user-level collection of AI agents that travel with you across projects. Unlike project agents (defined in a project's .squad/ directory), personal agents live in your global config directory and are automatically discovered when you start a squad session.
Directory Structure
~/Library/Application Support/squad/personal-squad/ # macOS
~/.config/squad/personal-squad/ # Linux
%APPDATA%/squad/personal-squad/ # Windows
├── agents/
│ ├── {agent-name}/
│ │ ├── charter.md
│ │ └── history.md
│ └── ...
└── config.json # Optional: personal squad config
How It Works
- Ambient Discovery: When Squad starts a session, it checks for a personal squad directory
- Merge: Personal agents are merged into the session cast alongside project agents
- Ghost Protocol: Personal agents can read project state but not write to it
- Kill Switch: Set
SQUAD_NO_PERSONAL=1to disable ambient discovery
Commands
squad personal init— Bootstrap a personal squad directorysquad personal list— List your personal agentssquad personal add {name} --role {role}— Add a personal agentsquad personal remove {name}— Remove a personal agentsquad cast— Show the current session cast (project + personal)
Ghost Protocol
See templates/ghost-protocol.md for the full rules. Key points:
- Personal agents advise; project agents execute
- No writes to project
.squad/state - Transparent origin tagging in logs
- Project agents take precedence on conflicts
Configuration
Optional config.json in the personal squad directory:
{
"defaultModel": "auto",
"ghostProtocol": true,
"agents": {}
}
Environment Variables
SQUAD_NO_PERSONAL— Set to any value to disable personal squad discoverySQUAD_PERSONAL_DIR— Override the default personal squad directory path
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 · 67 lines · 14 tokens per session scan A 991d18493e4d
personal-squad is a skill published in the GitHub repository github/gh-aw (5,091 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 515 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.
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.