Borrowing it
Nothing to install: this file belongs to webmaxru/is-ai-native. 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/webmaxru/is-ai-native/main/.copilot/skills/cross-squad/SKILL.mdgit clone --depth 1 https://github.com/webmaxru/is-ai-nativeWrote 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/webmaxru/is-ai-native/cross-squad)<a href="https://agentmods.dev/skills/webmaxru/is-ai-native/cross-squad"><img src="https://agentmods.dev/badge/skills/webmaxru/is-ai-native/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.
<a href="https://agentmods.dev/skills/webmaxru/is-ai-native/cross-squad"><img src="https://agentmods.dev/badge/skills/webmaxru/is-ai-native/cross-squad.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.01082 |
| Opus 5.5 | $0.00005 | $0.00433 |
| Sonnet 5.5 | $0.00002 | $0.00216 |
| Haiku 4.5 | $0.00001 | $0.00108 |
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.
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.
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.jsonin known org repos - Upstream config: Squads already listed in
.squad/upstream.jsonare checked for manifests - Explicit registry: A central
squad-registry.jsoncan 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 createin 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
- Title:
- Track: Record the cross-squad issue URL in the originating squad's orchestration log
- Poll: Periodically check if the delegated issue is closed/completed
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
cross-squad is a skill published in the GitHub repository webmaxru/is-ai-native (5 stars, last pushed 2mo ago), 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.
Other skills, from other repositories
speckit-workflow
Manage and run Spec Kit automation workflows via specify workflow. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use…
apex-workflow-start
Start or resume APEX work in VS Code Copilot. Select the interactive Orchestrator or domain owner, recover current project evidence, collect missing decisions and use native tasks without UI handoff or readiness rituals.
retro-enforcement
Ensure retrospectives happen on schedule and that their action items are tracked in GitHub Issues — not markdown checklists.
ralph-two-pass-scan
Cuts GitHub API calls by separating lightweight list scanning from full hydration.
coordinator-source-of-truth
The complete file-by-file source-of-truth hierarchy for Squad: which files are authoritative, which are derived/append-only, who may write each one, who may read each one, and the precedence rules when they conflict. Squad coordinator loads this on demand when it needs to resolve a write conflict, decide where a piece…
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…