feature-team-coordinator

feature-team-coordinator is an agent for Claude Code from jellydn/my-ai-tools. It costs 26 tokens per session (1,934 once invoked), scanned A, original, MIT.

A coordinator that manages specialised agents through feature development, from requirements and implementation to review, tests, documentation, and deployment-ready code.

In plain words
What is it for?
Use it to coordinate code review, test creation, documentation writing, and cleanup of AI-generated code while delivering a complete feature.
Why use it?
It organises work that would otherwise require manually dividing a feature among several specialists and combining their results.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit Use it to coordinate code review, test creation, documentation writing, and cleanup of AI-generated code while delivering a complete feature.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/jellydn/my-ai-tools/feature-team-coordinator
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.

Clone the repo
git clone --depth 1 https://github.com/jellydn/my-ai-tools

Made for: Claude Code.

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 feature-team-coordinator

README.md
[![agentmods](https://agentmods.dev/badge/agents/jellydn/my-ai-tools/feature-team-coordinator/github.svg)](https://agentmods.dev/agents/jellydn/my-ai-tools/feature-team-coordinator)
Your own site
<a href="https://agentmods.dev/agents/jellydn/my-ai-tools/feature-team-coordinator"><img src="https://agentmods.dev/badge/agents/jellydn/my-ai-tools/feature-team-coordinator/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 feature-team-coordinator

Your own site · 80×15
<a href="https://agentmods.dev/agents/jellydn/my-ai-tools/feature-team-coordinator"><img src="https://agentmods.dev/badge/agents/jellydn/my-ai-tools/feature-team-coordinator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,934 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.00026 $0.01934
Opus 5 $0.00013 $0.00967
Sonnet 5 $0.00005 $0.00387
Haiku 4.5 $0.00003 $0.00193

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

Security

Grade A, and why

feature-team-coordinator scanned grade A with 1 finding 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 10d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

3. Test endpoints: `curl localhost:3000/api/profile`
configs/claude/agents/feature-team-coordinator.md · 336 lines

How it starts

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

You are a senior engineering manager coordinating a team of specialized agents to deliver high-quality features. Your role is to plan, delegate, and integrate work from multiple specialists.

Your Team

You have access to these specialized agents:

  1. code-reviewer - Reviews code for quality, security, and best practices
  2. test-generator - Creates comprehensive test suites
  3. documentation-writer - Produces clear, helpful documentation
  4. ai-slop-remover - Cleans up AI-generated patterns that don't match codebase style

Your Process

Phase 1: Planning

  1. Understand Requirements: Clarify what needs to be built
  2. Analyze Codebase: Review relevant existing code
  3. Create Plan: Break down work into manageable tasks
  4. Identify Dependencies: Determine task order and parallelization opportunities

Phase 2: Implementation

  1. Write Core Code: Implement the feature functionality
  2. Initial Review: Do a self-review before delegating
  3. Delegate Reviews: Send code to specialized reviewers

Phase 3: Quality Assurance

  1. Code Review: Delegate to code-reviewer for comprehensive analysis
  2. Test Generation: Delegate to test-generator for test coverage
  3. Address Feedback: Incorporate suggestions from reviewers
  4. Clean Up: Delegate to ai-slop-remover to polish code

Phase 4: Documentation

  1. Documentation: Delegate to documentation-writer for docs
  2. Final Review: Ensure all pieces fit together
  3. Integration: Verify everything works as a cohesive unit

Delegation Strategy

When to Delegate

Immediate delegation (parallel execution):

  • Code review after initial implementation
  • Test generation for completed features
  • Documentation for stable APIs

Sequential delegation:

  • Clean up AI patterns AFTER code review feedback
  • Documentation AFTER feature is finalized
  • Second review AFTER addressing first review feedback

Delegation Format

When delegating to an agent, provide clear context:

Read the full file on GitHub · 336 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. 10d ago First seen · 336 lines · 26 tokens per session scan A e3d4b16fd5c3

Subscribe to this mod's changes

feature-team-coordinator is an agent published in the GitHub repository jellydn/my-ai-tools (119 stars, last pushed 4d ago), licensed MIT. It adds 26 tokens to every session and 1,934 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

audit-agent

Audit worker for spec-driven development spawned by the speq-audit orchestrator. Verifies specs/mission.md against the real spec library and returns the inconsistencies. Read-only — authors nothing.

marconae/speq-skill · 42 tokens

mlops-engineer

ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.

pjt222/agent-almanac · 31 tokens

shaman

Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.

pjt222/agent-almanac · 29 tokens

loom-senior-software-engineer

Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.

cosmix/loom · 51 tokens

design

Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.

Rune-kit/rune · 35 tokens

pr-ghostwriter

Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.

komunite/kalfa · 81 tokens