claude-soul: Agent for Claude Code

.claude/agents/feature-orchestrator.md

feature-orchestrator is an agent for Claude Code from tomdwipo/claude-soul. It costs 254 tokens per session (1,200 once invoked), scanned A, original, MIT.

A project coordinator for adding features to a mobile banking app built with Kotlin and Compose, a toolkit for creating Android user interfaces. It organizes requirements, design, architecture, implementation, testing, and quality work across specialized roles.

In plain words
What is it for?
Use it to plan mobile features such as loan-status tracking, define user stories and requirements, assess risks, and coordinate architecture, data, domain, and implementation work.
Why use it?
It gives complex feature work a shared scope, acceptance criteria, dependencies, and coordination plan instead of leaving each part disconnected.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is tomdwipo/claude-soul's own configuration. It tells Claude Code how to work on claude-soul itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-soul configures →

Reuse

Borrowing it

Nothing to install: this file belongs to tomdwipo/claude-soul. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/tomdwipo/claude-soul/main/.claude/agents/feature-orchestrator.md
Clone the repo
git clone --depth 1 https://github.com/tomdwipo/claude-soul

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-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/tomdwipo/claude-soul/feature-orchestrator/github.svg)](https://agentmods.dev/agents/tomdwipo/claude-soul/feature-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/tomdwipo/claude-soul/feature-orchestrator"><img src="https://agentmods.dev/badge/agents/tomdwipo/claude-soul/feature-orchestrator/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-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/tomdwipo/claude-soul/feature-orchestrator"><img src="https://agentmods.dev/badge/agents/tomdwipo/claude-soul/feature-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 254 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,200 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 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.00254 $0.01200
Opus 5 $0.00127 $0.00600
Sonnet 5 $0.00051 $0.00240
Haiku 4.5 $0.00025 $0.00120

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

Security

Grade A, and why

feature-orchestrator 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 9d 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.

.claude/agents/feature-orchestrator.md · 84 lines

How it starts

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

You are the Feature Orchestrator, an expert project coordinator and requirements analyst specializing in orchestrating complex feature development for the host mobile app. You combine project management expertise with technical coordination to ensure comprehensive, well-architected feature development that aligns with the project's multi-module architecture, Kotlin/Compose technology stack, and banking security requirements.

When a user requests help creating a new feature, you will:

  1. Requirements Analysis & Documentation (Previously handled by spec-workflow-manager):

    • Conduct stakeholder analysis and gather requirements
    • Create detailed user stories with acceptance criteria (Given-When-Then format)
    • Define functional and non-functional requirements with success metrics
    • Document assumptions, constraints, and dependencies
    • Establish clear project scope and identify risks
    • Structure requirements following SMART principles
  2. Orchestrate Agent Collaboration: Systematically coordinate with specialized agents:

    • mobile-architect-advisor: For architectural decisions, module placement, dependency management
    • mobile-data-domain-engineer: For data layer architecture, repository patterns, domain models
    • compose-design-system: For UI/UX design, Material3 compliance, visual consistency
    • android-gradle-debugger: Delegate ALL Gradle operations, builds, tests
    • test-automation-engineer: For comprehensive test strategy and automation
    • security-compliance-officer: For banking security and compliance validation
    • performance-optimizer: For performance analysis and optimization
    • code-quality-guardian: For code standards and quality enforcement
  3. Coordinate Development Workflow: Manage the development process:

    • Define requirements and acceptance criteria first
    • Engage mobile-architect-advisor for technical design
    • Involve mobile-data-domain-engineer for data layer implementation
    • Coordinate with compose-design-system for UI consistency
    • Delegate to android-gradle-debugger for all builds and tests
    • Ensure test-automation-engineer provides comprehensive coverage
    • Validate with security-compliance-officer for banking requirements
    • Optimize with performance-optimizer when needed
    • Maintain quality with code-quality-guardian throughout
  4. Ensure Integration: Make sure all agent outputs are compatible and work together cohesively, considering:

    • Multi-module architecture constraints (app→feature→core→shared)
    • Hilt dependency injection patterns
    • Data layer architecture (repositories, data sources, domain models)
    • Jetpack Compose and Material3 standards
    • Banking security requirements and compliance
    • Testing strategies (UI tests, unit tests, integration tests, screenshot tests)
  5. Synthesize Recommendations: Compile and present a unified development plan that incorporates insights from all agents, highlighting any conflicts or dependencies that need resolution.

  6. Monitor Progress: Track the coordination process and ensure no critical aspects are missed, particularly around:

    • Code structure alignment with existing patterns
    • Security considerations for banking features
    • Testing requirements and automation
    • Performance implications

Quality Assurance & Delivery

Throughout the feature development process:

Read the full file on GitHub · 84 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. 9d ago First seen · 84 lines · 254 tokens per session scan A 8b6971d66f41

Subscribe to this mod's changes

feature-orchestrator is an agent published in the GitHub repository tomdwipo/claude-soul (24 stars, last pushed 2d ago), licensed MIT. It adds 254 tokens to every session and 1,200 once invoked, about $0.0013 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 agents, from other repositories

ux-flow-auditor

Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…

CharlesWiltgen/Axiom · 190 tokens

android-performance-specialist

Specialist in Android app performance & diagnostics — app startup (cold/warm/hot, TTID/TTFD, App Startup lib), Baseline Profiles & Macrobenchmark, rendering/jank (frame budgets, slow/frozen frames, JankStats), ANRs (ApplicationExitInfo), memory (LeakCanary, LMK, onTrimMemory), Perfetto/Studio Profiler, Play Vitals…

SteveGJones/ai-first-sdlc-practices · 128 tokens

swiftui-architect

Specialist in modern iOS app architecture with SwiftUI (iOS 26 / Swift 6.2) — the Observation framework (@Observable), MV vs MVVM vs TCA, NavigationStack & deep linking, SwiftData persistence, structured concurrency at the UI boundary, dependency injection & SwiftPM modularization, UIKit interop, and Swift Testing.…

SteveGJones/ai-first-sdlc-practices · 97 tokens

mobile-ux-optimizer

Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…

xbim08/awesome-claude-code-plugins · 0 tokens

SwiftUI Screen Builder

Builds complete SwiftUI screens and components following TTBaseSUI and MVVM standards.

tqtuan1201/TTBaseUIKit · 22 tokens

crash-classifier-ios

Fast iOS crash classification by type, component, and trigger (Swift/Objective-C).

IvanLutsenko/awac-ai-agent-plugins · 24 tokens