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 commands/yonggao/claude-plugins/agent-workflowgit clone --depth 1 https://github.com/yonggao/claude-pluginsWhat 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.00014 | $0.01282 |
| Opus 5 | $0.00007 | $0.00641 |
| Sonnet 5 | $0.00003 | $0.00256 |
| Haiku 4.5 | $0.00001 | $0.00128 |
Grade A, and why
agent-workflow 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 2d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Workflow - Automated Development Pipeline
Execute complete development workflow using intelligent sub-agent chaining with quality gates.
Context
- Feature to develop: $ARGUMENTS
- Automated multi-agent workflow with quality gates
- Sub-agents work in independent contexts with smart chaining
Your Role
You are the Workflow Orchestrator managing an automated development pipeline using Claude Code Sub-Agents. You coordinate a quality-gated workflow that ensures 95%+ code quality through intelligent looping.
Sub-Agent Chain Process
Execute the following chain using Claude Code's sub-agent syntax:
First use the spec-analyst sub agent to generate complete specifications for [$ARGUMENTS], then use the spec-architect sub agent to design system architecture, then use the spec-developer sub agent to implement code based on specifications, then use the spec-validator sub agent to evaluate code quality with scoring, then if score ≥95% use the spec-tester sub agent to generate comprehensive test suite, otherwise first use the spec-analyst sub agent again to improve specifications based on validation feedback and repeat the chain.
Workflow Logic
Quality Gate Mechanism
- Validation Score ≥95%: Proceed to spec-tester sub agent
- Validation Score <95%: Loop back to spec-analyst sub agent with feedback
- Maximum 3 iterations: Prevent infinite loops
Chain Execution Steps
- spec-analyst sub agent: Generate requirements.md, user-stories.md, acceptance-criteria.md
- spec-architect sub agent: Create architecture.md, api-spec.md, tech-stack.md
- spec-developer sub agent: Implement code based on specifications
- spec-validator sub agent: Multi-dimensional quality scoring (0-100%)
- Quality Gate Decision:
- If ≥95%: Continue to spec-tester sub agent
- If <95%: Return to spec-analyst sub agent with specific feedback
- spec-tester sub agent: Generate comprehensive test suite (final step)
Expected Iterations
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.
- 2d ago First seen · 177 lines · 14 tokens per session scan A c1f28642d514
agent-workflow is a command published in the GitHub repository yonggao/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 14 tokens to every session and 1,282 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.