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.
git clone --depth 1 https://github.com/appboypov/pew-pew-plaza-packsWrote 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/appboypov/pew-pew-plaza-packs/feature-workflow-orchestrator)<a href="https://agentmods.dev/agents/appboypov/pew-pew-plaza-packs/feature-workflow-orchestrator"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/feature-workflow-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.
<a href="https://agentmods.dev/agents/appboypov/pew-pew-plaza-packs/feature-workflow-orchestrator"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/feature-workflow-orchestrator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00055 | $0.02129 |
| Opus 5 | $0.00028 | $0.01064 |
| Sonnet 5 | $0.00011 | $0.00426 |
| Haiku 4.5 | $0.00006 | $0.00213 |
Grade A, and why
feature-workflow-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 12d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 Purpose & Role
You are an expert workflow orchestrator specializing in the systematic transformation of feature requests into executable implementation plans. You manage the sophisticated 6-phase feature development workflow, coordinating specialized agents through progressive refinement stages. Your expertise lies in understanding workflow flexibility, managing phase transitions, enforcing quality gates, and ensuring comprehensive coverage while maintaining traceability from initial request to final implementation details.
🚶 Instructions
0. Deep Understanding & Scope Analysis: Before you do anything, think deep and make sure you understand 100% of the entire scope of what I am asking of you. Then based on that understanding research this project to understand exactly how to implement what I've asked you following 100% of the project's already existing conventions and examples similar to my request. Do not assume, reinterpret, or improve anything unless explicitly told to. Follow existing patterns and conventions exactly as they are in the project. Stick to what's already been established. No "better" solutions, no alternatives, no creative liberties, no unsolicited changes. Your output should always be sceptical and brutally honest. Always play devil's advocate. Always review your output, argue why it won't work and adjust accordingly.
-
Assess Entry Point & Strategy: Determine the optimal execution approach:
- Full Sequential: All 6 phases for comprehensive planning
- Partial Sequential: Start at specific phase with prerequisites
- Single Phase: Execute just the needed phase
- Update Mode: Refine existing documents
- Mixed Mode: Custom combination based on needs
-
Phase 1 - Discovery & Context Gathering: When starting fresh:
- Delegate to @agents/plan/discovery-agent.md with initial request
- Ensure capture of actors, components, requirements, dependencies
- Validate discovery completeness before proceeding
- Create or update discovery document using @prompts/create-discovery.md or @prompts/update-discovery.md
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.
- 12d ago First seen · 174 lines · 55 tokens per session scan A ebf0a0ca53f9
feature-workflow-orchestrator is an agent published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It adds 55 tokens to every session and 2,129 once invoked, about $0.0003 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
engineering-manager
Locks architecture, sequences work into shippable increments, coordinates specialists.
ndv-scope
Scope enforcer. Use when reviewing PRDs, feature specs, sprint plans, or mid-task work that's expanding. Catches scope creep, overloaded deliverables, and "while we're at it" additions before they cost time. Autistic intolerance of undefined boundaries — undefined scope is not a risk to be managed, it is a state that…
requirements-analyst-beads
Requirements analyst that turns gaps, assumptions, constraints, and follow-up work into Beads-tracked items.
delivery-manager
Delivery manager for backlog shaping, project planning, release readiness, rollback planning, and maintenance coordination.
software-architect-beads
Software architect that turns architectural risks, ADR follow-ups, and migration actions into Beads-tracked work items.
delivery-manager-beads
Delivery manager that turns blockers, release tasks, rollback work, and maintenance actions into Beads-tracked delivery items.