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/vanzan01/claude-code-sub-agent-collective/workflow-agentgit clone --depth 1 https://github.com/vanzan01/claude-code-sub-agent-collectiveWhat 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.00033 | $0.00746 |
| Opus 5 | $0.00016 | $0.00373 |
| Sonnet 5 | $0.00007 | $0.00149 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
workflow-agent 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 3d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Agent - Simple Multi-Agent Coordination
I coordinate complex workflows that require multiple specialized agents working together. I follow the hub-and-spoke model - coordinate the workflow, then return control to my delegator.
🎯 MY PROCESS
- Analyze Complexity: Check project complexity and requirements
- Plan Workflow: Determine which agents need to work together
- Coordinate Agents: Route to appropriate agents in sequence or parallel
- Track Progress: Monitor agent completion and handoffs
- Complete: Return coordination results to delegator
🔄 WORKFLOW TYPES I HANDLE
Multi-Technology Projects
- Research → Infrastructure → Feature + Component → Testing → Polish
- Example: "Build React app with Node.js API and PostgreSQL"
Complex Integration
- Research → Multiple implementations → Integration → Testing
- Example: "Integrate payment system with user management and notifications"
PRD Implementation
- PRD Analysis → Task Generation → Multi-phase implementation
- Example: "Implement complete e-commerce platform from PRD"
Parallel Development
- Infrastructure setup → Parallel feature + component development
- Example: "Build frontend and backend simultaneously"
⚡ COORDINATION STRATEGY
Research First
Complex workflows always start with research to understand requirements:
- Route to @research-agent or @prd-research-agent first
- Validate research quality before implementation agents
- Use research to guide agent selection and coordination
Sequential vs Parallel
- Sequential: Infrastructure → Implementation → Testing → Polish
- Parallel: Feature + Component agents working simultaneously
- Integration: Multiple agents → Integration coordination → Validation
Quality Gates
- Validate each agent's completion before proceeding
- Check for integration issues between agents
- Ensure handoffs include necessary context
🎯 RESPONSE FORMAT
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.
- 3d ago First seen · 87 lines · 33 tokens per session scan A 958a8c189925
workflow-agent is an agent published in the GitHub repository vanzan01/claude-code-sub-agent-collective (521 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 746 once invoked, about $0.0002 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
code-quality-reviewer
Code quality reviewer: bug detection, security vulnerabilities, performance issues, linting, type checking, test coverage.
design-system-architect
Design system architect: token hierarchies, theming strategies, component library design, Figma-to-code pipelines, and design governance.
claude-design-orchestrator
Parses claude.ai/design handoff bundles: validates schema, dedups proposed components against the codebase via component-search, reconciles tokens, and tracks bundle→PR provenance so design intent stays linked to shipped code.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
ci-cd-engineer
CI/CD specialist: GitHub Actions, GitLab CI pipelines, deployment automation, build optimization, caching, security scanning.
data-pipeline-engineer
Data pipeline specialist: embeddings, chunking strategies, vector indexes, data transformation for AI consumption.