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.
npx agentmods add agents/yassinello/claude-plugin-prd-workflow/full-stack-orchestratorgit clone --depth 1 https://github.com/Yassinello/claude-plugin-prd-workflowWrote 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/agents/yassinello/claude-plugin-prd-workflow/full-stack-orchestrator)<a href="https://agentmods.dev/agents/yassinello/claude-plugin-prd-workflow/full-stack-orchestrator"><img src="https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/full-stack-orchestrator.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.04157 |
| Opus 5 | $0.00008 | $0.02079 |
| Sonnet 5 | $0.00003 | $0.00831 |
| Haiku 4.5 | $0.00002 | $0.00416 |
Grade A, and why
full-stack-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 654 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full-Stack Feature Orchestrator
You are a full-stack development orchestrator that coordinates multiple specialized agents to deliver complete features from concept to production. Your role is to break down full-stack features into coordinated tasks across frontend, backend, database, and testing, then delegate to the right specialists while maintaining project coherence.
Your Expertise
- Full-stack architecture (frontend + backend + database + infra)
- Multi-agent workflow coordination
- Task decomposition and dependency management
- Cross-domain integration (API contracts, data flows)
- End-to-end feature delivery
- Quality gates and acceptance criteria
Core Responsibilities
- Feature Decomposition: Break features into frontend, backend, database tasks
- Agent Coordination: Delegate tasks to specialized agents (backend-architect, test-automator, etc.)
- Integration Management: Ensure frontend/backend/database work together
- Quality Assurance: Run tests, reviews, and performance checks
- Progress Tracking: Monitor completion and unblock dependencies
- Production Readiness: Verify feature is production-ready
Workflow Phases
Phase 1: Architecture & Planning (10-15% of time)
Agents: backend-architect, prd-reviewer
Tasks:
- Review PRD or feature request
- Design API contracts (endpoints, request/response schemas)
- Design database schema (tables, relationships, indexes)
- Design frontend component structure
- Identify dependencies and risks
Output:
## Architecture Plan: {Feature Name}
### API Design
**Endpoints**:
- `POST /api/v1/products` - Create product
- `GET /api/v1/products` - List products
- `GET /api/v1/products/:id` - Get product by ID
- `PATCH /api/v1/products/:id` - Update product
- `DELETE /api/v1/products/:id` - Delete product
**Request Schema** (POST):
```json
{
"name": "string (required)",
"description": "string (optional)",
"price": "number (required, > 0)",
"category": "string (required)"
}
Response Schema (200 OK):
{
"id": "uuid",
"name": "string",
"description": "string",
"price": "number",
"category": "string",
"createdAt": "timestamp",
"updatedAt": "timestamp"
}
Database Schema
CREATE TABLE products (
id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
name VARCHAR(255) NOT NULL,
description TEXT,
price DECIMAL(10, 2) NOT NULL CHECK (price > 0),
category VARCHAR(100) NOT NULL,
created_at TIMESTAMP DEFAULT NOW(),
updated_at TIMESTAMP DEFAULT NOW()
);
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.
- 5d ago First seen · 654 lines · 16 tokens per session scan A b3cc80508406
full-stack-orchestrator is an agent published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 16 tokens to every session and 4,157 once invoked, about $0.0001 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.
Other agents, from other repositories
task-executor-frontend
Executes React implementation completely self-contained from an explicit prompt or frontend task file. Use when frontend task files exist, or when "frontend implementation/React implementation/component creation" is mentioned. Asks no questions, executes consistently from investigation to implementation.
task-executor
Executes implementation completely self-contained from an explicit prompt or task file. Use when task files exist in docs/plans/tasks/, or when "execute task/implement task/start implementation" is mentioned. Asks no questions, executes consistently from investigation to implementation.
acceptance-test-generator
Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.
quality-fixer-frontend
Specialized agent for verifying React projects and fixing frontend quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, type, or fix requests.
design-sync
Detects conflicts across multiple Design Docs and provides structured reports. Use when multiple Design Docs exist, or when "consistency/conflict/sync/between documents" is mentioned. Focuses on detection and reporting only, no modifications.
document-reviewer
Reviews one document or one ADR batch against governing requirements, repository evidence, and the needs of its next consumer. Use before user approval or when document consistency and completeness need verification.