team-coordination

team-coordination is a skill for Claude Code, Codex from bybren-llc/safe-agentic-workflow. It costs 71 tokens per session (1,537 once invoked), scanned A, original, MIT.

A coordination guide for teams of coding agents working in SAFe, a framework for organising software delivery into roles, stages, and quality checks. It covers shared task lists, agent communication, dependencies, and multi-agent workflows.

In plain words
What is it for?
Use it to create and coordinate agent teams, assign work across roles such as frontend, backend, and testing, enforce dependencies and quality gates, and run parallel reviews or investigations.
Why use it?
It helps several agents work on one feature without losing track of ownership, order, or required checks. It also clarifies when to use agent teams, subagents, or background agents.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; installed under .agents/ (shared by several agents); mentions AGENTS.md.

Good fit Use it to create and coordinate agent teams, assign work across roles such as frontend, backend, and testing, enforce dependencies and quality gates, and run parallel reviews or investigations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bybren-llc/safe-agentic-workflow/team-coordination
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 bybren-llc/safe-agentic-workflow --skill team-coordination
Clone the repo
git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow

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 team-coordination

README.md
[![agentmods](https://agentmods.dev/badge/skills/bybren-llc/safe-agentic-workflow/team-coordination.svg)](https://agentmods.dev/skills/bybren-llc/safe-agentic-workflow/team-coordination)
Your own site
<a href="https://agentmods.dev/skills/bybren-llc/safe-agentic-workflow/team-coordination"><img src="https://agentmods.dev/badge/skills/bybren-llc/safe-agentic-workflow/team-coordination.svg" alt="Measured on agentmods" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,537 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found 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.00071 $0.01537
Opus 5 $0.00036 $0.00768
Sonnet 5 $0.00014 $0.00307
Haiku 4.5 $0.00007 $0.00154

Measured 8d ago against content hash fda05f75501e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

team-coordination 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 8d 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

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/skills/team-coordination/SKILL.md · 206 lines

How it starts

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

Team Coordination Skill

TEMPLATE: This skill uses {{PLACEHOLDER}} tokens. Replace with your project values before use.

Purpose

Orchestrate multi-agent teams for SAFe workflows. This skill provides patterns for spawning teams, assigning work by role, enforcing quality gates via task dependencies, and managing the full delivery pipeline.

Prerequisites

Agent Teams may be experimental depending on provider. Enable as required:

// Provider-specific settings
{
  "env": {
    "AGENT_TEAMS_ENABLED": "1"
  }
}

When This Skill Applies

  • Orchestrating work across multiple agent roles (FE, BE, QAS, etc.)
  • Spawning a team for a Feature or Epic-level deliverable
  • Coordinating parallel implementation with quality gate enforcement
  • Running competing hypothesis debugging with multiple agents
  • Performing parallel code review across security, performance, and test coverage

Agent Teams vs Subagents vs Background Agents

Approach Communication Coordination Best For
Agent Teams DMs, broadcasts Shared TaskList with dependencies Complex multi-role SAFe workflows
Subagents Report back only Main agent manages Focused tasks, results only
Background Agents None None Fire-and-forget parallel work

Use Agent Teams when: teammates need to share findings, challenge each other, and coordinate via SAFe gates. Use Subagents when: you need quick, focused workers that report back. Use Background Agents when: tasks are independent and do not need coordination.

SAFe Team Patterns

Pattern 1: TDM as Team Lead

The TDM (Technical Delivery Manager) is the natural team lead in the 11-agent model:

Create an agent team for {{TICKET_PREFIX}}-XXX implementation.

Team lead (TDM) responsibilities:
- Spawn teammates by role (BE, FE, QAS, etc.)
- Create tasks with SAFe gate dependencies
- Monitor progress and steer teammates
- Synthesize results and escalate blockers

Spawn these teammates:
- BE Developer: Implement API endpoints per spec
- FE Developer: Implement UI components per spec
- QAS: Validate acceptance criteria after implementation

Read the full file on GitHub · 206 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 8d ago First seen · 206 lines · 71 tokens per session scan A fda05f75501e

Subscribe to this mod's changes

team-coordination is a skill published in the GitHub repository bybren-llc/safe-agentic-workflow (406 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,537 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

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

bug-triage

Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.

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

bug-report

Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.

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

playtest-report

Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

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

security-audit

Java security checklist covering OWASP Top 10, input validation, injection prevention, and secure coding. Works with Spring, Quarkus, Jakarta EE, and plain Java. Use when reviewing code security, before releases, or when user asks about vulnerabilities.

decebals/claude-code-java · 55 tokens

issue-triage

Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.

decebals/claude-code-java · 44 tokens