bradygaster/squad is a tool that creates a human-directed team of AI development agents inside a project repository through GitHub Copilot. Developers use it to delegate work among persistent specialists such as frontend, backend, testing, and lead agents while retaining responsibility for decisions and review. The catalogue entries are the skills, agents, and instructions that define and coordinate those team members.
Borrowing it
Nothing to install: this file belongs to bradygaster/squad. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bradygaster/squad/dev/.squad/skills/work-monitoring/SKILL.mdgit clone --depth 1 https://github.com/bradygaster/squadWrote 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/bradygaster/squad/work-monitoring)<a href="https://agentmods.dev/skills/bradygaster/squad/work-monitoring"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/work-monitoring/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/skills/bradygaster/squad/work-monitoring"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/work-monitoring.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.00014 | $0.00356 |
| Opus 5.5 | $0.00006 | $0.00142 |
| Sonnet 5.5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
work-monitoring 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 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.
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.
What it actually says
Work Monitoring
Use this skill when monitoring Squad issues, pull requests, CI, review feedback, or a labeled work queue.
Scope
- Start with a named repository, explicit workstream, label set, and state filter.
- Produce monitoring reports, triage summaries, and narrowly scoped coordination actions.
- Do not turn monitoring into product implementation or broad cleanup.
Procedure
- List candidates using the narrowest available filters.
- Hydrate every candidate before mutating it; list results alone are not sufficient evidence.
- Prioritize untriaged work, assigned work, CI failures, review feedback, and approved pull requests according to the active request.
- Route domain work to the accountable specialist in
.squad/routing.md. - After every mutation, refetch the exact item and verify the requested transition and fields.
- Stop immediately on a verification mismatch; do not continue with later mutations.
- Use the focused two-pass scan for broad retrieval, then inspect only actionable candidates.
Stop Conditions
- Stop before mutation when the workstream, labels, repository, or state filter is ambiguous.
- Stop when candidates cannot be hydrated or post-mutation state cannot be verified.
- Stop when an action would exceed the explicitly scoped queue or become product work.
Anti-Patterns
- Applying bulk changes from a generic label alone.
- Closing, relabeling, assigning, or deleting based only on list output.
- Treating Ralph's monitoring role as authorization to modify product artifacts.
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 Changed · -11 lines d4e63f6b0837
- 1mo ago First seen · 53 lines · 14 tokens per session scan A fdb3936956ea
work-monitoring is a skill published in the GitHub repository bradygaster/squad (3,295 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 356 once invoked, about $0.0001 per session on Opus 5.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-12.
Other skills, from other repositories
gh
You have access to gh (GitHub CLI) for repository and project management.
pm-pr-workflow
Branch protection and PR creation workflow.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…