squad: Skill for Claude Code

.copilot/skills/architectural-proposals/SKILL.md

architectural-proposals is a skill for Claude Code, Codex from bradygaster/squad. It costs 18 tokens per session (1,430 once invoked), scanned A, a copy of architectural-proposals, MIT.

A writing pattern for architectural proposals, which describe important software structure decisions before implementation begins. It covers the problem, proposed design, impact, risks, scope, and decisions that need agreement.

In plain words
What is it for?
Writing proposals for architecture changes, new foundations, changing product direction, multi-stage projects, or updates to external dependencies.
Why use it?
It helps a team align on changes that could affect multiple parts of a codebase before spending time writing or refactoring code.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is bradygaster/squad's own configuration. It tells Claude Code and Codex how to work on squad itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything squad configures →

About the project

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.

bradygaster/squad · 3,327 stars · on GitHub · bradygaster.github.io

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/bradygaster/squad/dev/.copilot/skills/architectural-proposals/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/bradygaster/squad

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for architectural-proposals

README.md
[![agentmods](https://agentmods.dev/badge/skills/bradygaster/squad/architectural-proposals/github.svg)](https://agentmods.dev/skills/bradygaster/squad/architectural-proposals)
Your own site
<a href="https://agentmods.dev/skills/bradygaster/squad/architectural-proposals"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/architectural-proposals/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.

agentmods 80×15 button for architectural-proposals

Your own site · 80×15
<a href="https://agentmods.dev/skills/bradygaster/squad/architectural-proposals"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/architectural-proposals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,430 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.01430
Opus 5.5 $0.00007 $0.00572
Sonnet 5.5 $0.00004 $0.00286
Haiku 4.5 $0.00002 $0.00143

Measured 1mo ago against content hash 87cef2c5c3a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

architectural-proposals 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.

Origin

This is a copy

100% identical to architectural-proposals — 2 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.

.copilot/skills/architectural-proposals/SKILL.md · 152 lines

How it starts

The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Context

Proposals create alignment before code is written. Cheaper to change a doc than refactor code. Use this pattern when:

  • Architecture shifts invalidate existing assumptions
  • Product direction changes require new foundation
  • Multiple waves/milestones will be affected by a decision
  • External dependencies (Copilot CLI, SDK APIs) change

Patterns

Proposal Structure (docs/proposals/)

Required sections:

  1. Problem Statement — Why current state is broken (specific, measurable evidence)
  2. Proposed Architecture — Solution with technical specifics (not hand-waving)
  3. What Changes — Impact on existing work (waves, milestones, modules)
  4. What Stays the Same — Preserve existing functionality (no regression)
  5. Key Decisions Needed — Explicit choices with recommendations
  6. Risks and Mitigations — Likelihood + impact + mitigation strategy
  7. Scope — What's in v1, what's deferred (timeline clarity)

Optional sections:

  • Implementation Plan (high-level milestones)
  • Success Criteria (measurable outcomes)
  • Open Questions (unresolved items)
  • Appendix (prior art, alternatives considered)

Tone Ceiling Enforcement

Always:

  • Cite specific evidence (user reports, performance data, failure modes)
  • Justify recommendations with technical rationale
  • Acknowledge trade-offs (no perfect solutions)
  • Be specific about APIs, libraries, file paths

Never:

  • Hype ("revolutionary", "game-changing")
  • Hand-waving ("we'll figure it out later")
  • Unsubstantiated claims ("users will love this")
  • Vague timelines ("soon", "eventually")

Wave Restructuring Pattern

When a proposal invalidates existing wave structure:

  1. Acknowledge the shift: "This becomes Wave 0 (Foundation)"
  2. Cascade impacts: Adjust downstream waves (Wave 1, Wave 2, Wave 3)
  3. Preserve non-blocking work: Identify what can proceed in parallel
  4. Update dependencies: Document new blocking relationships

Example (Interactive Shell):

  • Wave 0 (NEW): Interactive Shell — blocks all other waves
  • Wave 1 (ADJUSTED): npm Distribution — shell bundled in cli.js
  • Wave 2 (DEFERRED): SquadUI — waits for shell foundation
  • Wave 3 (ADJUSTED): Public Docs — now documents shell as primary interface

Read the full file on GitHub · 152 lines

Changes

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.

  1. 1mo ago Changed 87cef2c5c3a5
  2. 2mo ago First seen · 152 lines · 18 tokens per session scan A 45719db4cb9b

Subscribe to this mod's changes

architectural-proposals is a skill published in the GitHub repository bradygaster/squad (3,327 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 1,430 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to architectural-proposals, differing in 2 lines, and is treated as a copy.

Related

architectural-proposals compared with skills from other repositories

architectural-proposals next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
architectural-proposalsbradygaster/squadSkill3.3kyesterdayMITA18Claude Code, Codex
ponytail-gaindmae97/omkSkill151yesterdayMITA83Claude Code, Codex
omk-mcp-setupdmae97/omkSkill151yesterdayMITA42Claude Code, Codex
Video Downloader (yt-dlp)tubecreate/tubecliSkill174yesterdayMITA21Claude Code, Codex
clean-architecture-dotnetSebastienDegodez/copilot-instructionsSkill1991mo agoApache-2.0A50Claude Code, Codex
outside-in-tddSebastienDegodez/copilot-instructionsSkill1991mo agoApache-2.0A35Claude Code, Codex
searching-textSebastienDegodez/copilot-instructionsSkill1991mo agoApache-2.0A28Claude Code, Codex