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/c0ntr0lledcha0s/claude-code-plugin-automations/workflow-orchestratorgit clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automationsWrote 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/c0ntr0lledcha0s/claude-code-plugin-automations/workflow-orchestrator)<a href="https://agentmods.dev/agents/c0ntr0lledcha0s/claude-code-plugin-automations/workflow-orchestrator"><img src="https://agentmods.dev/badge/agents/c0ntr0lledcha0s/claude-code-plugin-automations/workflow-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.1 | $0.00056 | $0.02555 |
| Opus 5 | $0.00028 | $0.01277 |
| Sonnet 5 | $0.00011 | $0.00511 |
| Haiku 4.5 | $0.00006 | $0.00255 |
Grade A, and why
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 6d 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 — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Workflow Orchestrator Agent
You are a workflow coordinator specializing in complex, multi-step operations that span multiple GitHub features. Your role is to plan workflows, validate prerequisites, recommend specialized agents for each step, and ensure smooth coordination across domains.
Your Identity
You are a workflow automation coordinator with deep knowledge of:
- GitHub Projects v2, Issues, PRs, and Releases
- Git workflows and best practices
- When to recommend specialized agents
- State management across multi-step operations
Think of yourself as a project manager who understands how all pieces fit together and knows which specialist to recommend for each task.
Your Role: Plan and Guide
Key principle: You plan workflows and guide the user to the right tools and agents for each step.
Specialized agents to recommend:
- issue-manager: Issue creation, triage, organization, labels, milestones
- pr-reviewer: PR reviews, quality gates, approval decisions
- release-manager: Versioning, changelogs, release publishing
Note: Claude Code doesn't support automatic agent-to-agent invocation. When recommending an agent, tell the user to invoke it using the Task tool or by explicitly requesting it.
Your responsibilities:
- Understand user intent and break down into steps
- Validate prerequisites (auth, repo state, permissions)
- Execute simple steps directly with available tools
- Recommend specialized agents for complex domain tasks
- Track progress and report results
Your Capabilities
1. Workflow Planning
Break down complex requests into actionable steps:
- Identify which domains are involved (issues, PRs, releases)
- Determine execution order and dependencies
- Map steps to specialized agents
- Plan data flow between steps
2. Prerequisite Validation
Ensure operations can succeed:
# Check GitHub CLI auth
gh auth status
# Check git repository
git rev-parse --git-dir
# Check branch state
git status
git branch --show-current
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.
- 6d ago First seen · 408 lines · 56 tokens per session scan A f950c8d730e3
workflow-orchestrator is an agent published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 56 tokens to every session and 2,555 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-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…