Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/yonggao/claude-pluginsnpx agentmods add commands/yonggao/claude-plugins/agent-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/commands/yonggao/claude-plugins/agent-workflow)<a href="https://agentmods.dev/commands/yonggao/claude-plugins/agent-workflow"><img src="https://agentmods.dev/badge/commands/yonggao/claude-plugins/agent-workflow/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/commands/yonggao/claude-plugins/agent-workflow"><img src="https://agentmods.dev/badge/commands/yonggao/claude-plugins/agent-workflow.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.00014 | $0.01282 |
| Opus 5.5 | $0.00006 | $0.00513 |
| Sonnet 5.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 2mo 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.
- 2mo 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 10mo ago), licensed MIT. It adds 14 tokens to every session and 1,282 once invoked, about $0.0001 per session on Opus 5.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.
agent-workflow compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| agent-workflowyonggao/claude-plugins | Command | 2 | 10mo ago | MIT | A | 14 | Claude Code |
| checklistgithub/spec-kit | Command | 150k | 2d ago | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 150k | 2d ago | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 150k | 2d ago | MIT | A | 13 | Claude Code |
| convergegithub/spec-kit | Command | 150k | 2d ago | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 150k | 2d ago | MIT | A | 14 | Claude Code |
| speckit.bug.fixgithub/spec-kit | Command | 150k | 2d ago | MIT | A | 12 | Claude Code |