team-composition-patterns SKILL.md skillA
team-composition-patterns from wshobson/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wshobson/agents/team-composition-patterns@v1.0.2Pins v1.0.2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wshobson/agents
- Path
plugins/agent-teams/skills/team-composition-patterns/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.2, committed May 17, 2026
- First version recorded
- Mar 26, 2026
- Size
- 8,168 bytes
- Repository stars
- 41,220
- License
- MIT
Design optimal agent team compositions with sizing heuristics, preset configurations, and agent type selection. Use this skill when deciding how many agents to spawn for a task, when choosing between a review team versus a feature team versus a debug team, when selecting the correct subagent_type for each role to ensure agents have the tools they need, when configuring display modes (tmux, iTerm2, in-process) for a CI or local environment, or when building a custom team composition for a…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Team Composition Patterns Best practices for composing multi-agent teams, selecting team sizes, choosing agent types, and configuring display modes for Claude Code's Agent Teams feature. ## When to Use This Skill - Deciding how many teammates to spawn for a task - Choosing between preset team configurations - Selecting the right agent type (subagent_type) for each role - Configuring teammate display modes (tmux, iTerm2, in-process) - Building custom team compositions for non-standard workflows ## Team Sizing Heuristics | Complexity | Team Size | When to Use | | ------------ | --------- | ----------------------------------------------------------- | | Simple | 1-2 | Single-dimension review, isolated bug, small feature | | Moderate | 2-3 | Multi-file changes, 2-3 concerns, medium features | | Complex | 3-4 | Cross-cutting concerns, large features, deep debugging | | Very Complex | 4-5 | Full-stack features, comprehensive reviews, systemic issues | …
Read the whole file at its exact version.
How to install
mdr add wshobson/agents/team-composition-patterns@sha256:e158dd0e38d875f7The line at the top of this page pins the label v1.0.2, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_t3acj2xbyxrr7hhd)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Mar 26, 2026 and May 17, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.2 latest | 2026-05-17 | 08ded5e | 8,168 B | A | view · diff |
| v1.0.2 | 2026-04-08 | 03d0b4b | 8,055 B | A | view · diff |
| v1.0.2 | 2026-04-08 | e98c1ae | 8,052 B | A | view · diff |
| v1.0.2 | 2026-04-04 | dcaa27d | 6,061 B | A | view · diff |
| v1.0.2 | 2026-03-26 | 840d219 | 8,049 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8168 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wshobson/agents · 41,220 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t3acj2xbyxrr7hhd GET https://markdownregistry.com/api/v1/resolve?ref=wshobson/agents/team-composition-patterns GET https://markdownregistry.com/api/v1/blob/e158dd0e38d875f7efd8d22fc00f800293585c9a44cce7c0715715f87feb164a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.