A coordination method for multiple Squad teams working across different repositories. Each squad publishes a small manifest describing its name, capabilities, and contact details so other squads can discover it.

Use it when a feature spans repositories, an architecture decision affects several teams, or one squad needs infrastructure or support from another.

It helps teams find the owner of a capability or request when work crosses repository or team boundaries. It supports handoffs without tightly connecting the squads together.

cross-squad — Skill for Claude Code and Codex by alonf/specrew

Install

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.

Any agent

npx skills add alonf/specrew --skill cross-squad

Clone the repo

git clone --depth 1 https://github.com/alonf/specrew

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/alonf/specrew/cross-squad/github.svg)](https://agentmods.dev/skills/alonf/specrew/cross-squad)

Your own site

<a href="https://agentmods.dev/skills/alonf/specrew/cross-squad"><img src="https://agentmods.dev/badge/skills/alonf/specrew/cross-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/alonf/specrew/cross-squad"><img src="https://agentmods.dev/badge/skills/alonf/specrew/cross-squad.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,082 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.

Model	Per session	Once invoked
Fable 5.1	$0.00012	$0.01082
Opus 5.5	$0.00005	$0.00433
Sonnet 5.5	$0.00002	$0.00216
Haiku 4.5	$0.00001	$0.00108

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

Security

Grade A, and why

cross-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 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 cross-squad — 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.

.copilot/skills/cross-squad/SKILL.md · 115 lines

How it starts

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

Context

When an organization runs multiple Squad instances (e.g., platform-squad, frontend-squad, data-squad), those squads need to discover each other, share context, and hand off work across repository boundaries. This skill teaches agents how to coordinate across squads without creating tight coupling.

Cross-squad orchestration applies when:

A task requires capabilities owned by another squad
An architectural decision affects multiple squads
A feature spans multiple repositories with different squads
A squad needs to request infrastructure, tooling, or support from another squad

Patterns

Discovery via Manifest

Each squad publishes a .squad/manifest.json declaring its name, capabilities, and contact information. Squads discover each other through:

Well-known paths: Check .squad/manifest.json in known org repos
Upstream config: Squads already listed in .squad/upstream.json are checked for manifests
Explicit registry: A central squad-registry.json can list all squads in an org

{
  "name": "platform-squad",
  "version": "1.0.0",
  "description": "Platform infrastructure team",
  "capabilities": ["kubernetes", "helm", "monitoring", "ci-cd"],
  "contact": {
    "repo": "org/platform",
    "labels": ["squad:platform"]
  },
  "accepts": ["issues", "prs"],
  "skills": ["helm-developer", "operator-developer", "pipeline-engineer"]
}

Context Sharing

When delegating work, share only what the target squad needs:

Capability list: What this squad can do (from manifest)
Relevant decisions: Only decisions that affect the target squad
Handoff context: A concise description of why this work is being delegated

Do NOT share:

Internal team state (casting history, session logs)
Full decision archives (send only relevant excerpts)
Authentication credentials or secrets

Work Handoff Protocol

Check manifest: Verify the target squad accepts the work type (issues, PRs)
Create issue: Use gh issue create in the target repo with:
- Title: [cross-squad] <description>
- Label: squad:cross-squad (or the squad's configured label)
- Body: Context, acceptance criteria, and link back to originating issue
Track: Record the cross-squad issue URL in the originating squad's orchestration log
Poll: Periodically check if the delegated issue is closed/completed

Read the full file on GitHub · 115 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.

1mo ago First seen · 115 lines · 12 tokens per session scan A 8536742a495b

Subscribe to this mod's changes

cross-squad is a skill published in the GitHub repository alonf/specrew (54 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 1,082 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 cross-squad, differing in 0 lines, and is treated as a copy.

Building agents Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens