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/.copilot/skills/agent-conduct/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/agent-conduct)<a href="https://agentmods.dev/skills/bradygaster/squad/agent-conduct"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/agent-conduct/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/agent-conduct"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/agent-conduct.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.00012 | $0.00293 |
| Opus 5.5 | $0.00005 | $0.00117 |
| Sonnet 5.5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
agent-conduct 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.
This is a copy
100% identical to agent-conduct — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Context
Every squad agent must follow these two hard rules. They were previously duplicated in every charter. Now they live here as a shared skill, loaded once.
Patterns
Product Isolation Rule (hard rule)
Tests, CI workflows, and product code must NEVER depend on specific agent names from any particular squad. "Our squad" must not impact "the squad." No hardcoded references to agent names (Flight, EECOM, FIDO, etc.) in test assertions, CI configs, or product logic. Use generic/parameterized values. If a test needs agent names, use obviously-fake test fixtures (e.g., "test-agent-1", "TestBot").
Peer Quality Check (hard rule)
Before finishing work, verify your changes don't break existing tests. Run the test suite for files you touched. If CI has been failing, check your changes aren't contributing to the problem. When you learn from mistakes, update your history.md.
Anti-Patterns
- Don't hardcode dev team agent names in product code or tests
- Don't skip test verification before declaring work done
- Don't ignore pre-existing CI failures that your changes may worsen
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 · 25 lines · 12 tokens per session scan A 898443cfbdd1
agent-conduct is a skill published in the GitHub repository bradygaster/squad (3,295 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 293 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-conduct, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
ponytail-gain
Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".
clean-architecture-dotnet
Use when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD patterns (invariants and events).
Video Downloader (yt-dlp)
Download videos from YouTube, TikTok, and 50+ platforms.
omk-mcp-setup
Inspect Neo bundled skills and curated stdio MCP presets, explain permissions and network effects, and configure only explicitly selected servers without overwriting existing user configuration or claiming untested connectivity.
outside-in-tdd
Use when writing tests from the outside-in, defining behavior before code, or any feature where tests should start from observable business behavior and let internal design emerge.
searching-text
Use when searching for text patterns across files, finding specific code locations, or getting lines with surrounding context in a single call.