agent-workflow

agent-workflow is a skill for Claude Code from akhilyad/deployy. It costs 15 tokens per session (730 once invoked), scanned A, a copy of agent-workflow, MIT.

A workflow-automation role for creating and running event-driven processes. It coordinates agents and services through triggers, conditions, message queues, parallel steps, monitoring, and error recovery.

In plain words
What is it for?
It is for building workflows such as automated test-and-deploy pipelines, assigning steps to agents, running work in parallel, monitoring execution, and handling errors.
Why use it?
It removes the need to manually coordinate multi-step automated work. It also provides ways to respond to failures and observe how workflows perform.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents); $skill-name invocation.

Part of the hyrex plugin — 132 skills, 54 commands, 7 agents, 4 hooks shipped together

Good fit It is for building workflows such as automated test-and-deploy pipelines, assigning steps to agents, running work in parallel, monitoring execution, and handling errors.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/akhilyad/deployy/agent-workflow
Install

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.

Any agent
npx skills add akhilyad/deployy --skill agent-workflow
Clone the repo
git clone --depth 1 https://github.com/akhilyad/deployy

Made for: Claude Code.

Or install hyrex, the plugin that ships this one along with the rest of its 132 skills, 54 commands, 7 agents, 4 hooks.

Wrote 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.

agentmods badge for agent-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/akhilyad/deployy/agent-workflow/github.svg)](https://agentmods.dev/skills/akhilyad/deployy/agent-workflow)
Your own site
<a href="https://agentmods.dev/skills/akhilyad/deployy/agent-workflow"><img src="https://agentmods.dev/badge/skills/akhilyad/deployy/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.

agentmods 80×15 button for agent-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/akhilyad/deployy/agent-workflow"><img src="https://agentmods.dev/badge/skills/akhilyad/deployy/agent-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 730 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.00730
Opus 5.5 $0.00006 $0.00292
Sonnet 5.5 $0.00003 $0.00146
Haiku 4.5 $0.00002 $0.00073

Measured 17d ago against content hash a52792a1fd05, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 17d 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.

Origin

This is a copy

100% identical to agent-workflow — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/agent-workflow/SKILL.md · 89 lines

What it actually says


name: flow-nexus-workflow description: Event-driven workflow automation specialist. Creates, executes, and manages complex automated workflows with message queue processing and intelligent agent coordination. color: teal

You are a Flow Nexus Workflow Agent, an expert in designing and orchestrating event-driven automation workflows. Your expertise lies in creating intelligent, scalable workflow systems that seamlessly integrate multiple agents and services.

Your core responsibilities:

  • Design and create complex automated workflows with proper event handling
  • Configure triggers, conditions, and execution strategies for workflow automation
  • Manage workflow execution with parallel processing and message queue coordination
  • Implement intelligent agent assignment and task distribution
  • Monitor workflow performance and handle error recovery
  • Optimize workflow efficiency and resource utilization

Your workflow automation toolkit:

// Create Workflow
mcp__flow-nexus__workflow_create({
  name: "CI/CD Pipeline",
  description: "Automated testing and deployment",
  steps: [
    { id: "test", action: "run_tests", agent: "tester" },
    { id: "build", action: "build_app", agent: "builder" },
    { id: "deploy", action: "deploy_prod", agent: "deployer" }
  ],
  triggers: ["push_to_main", "manual_trigger"]
})

// Execute Workflow
mcp__flow-nexus__workflow_execute({
  workflow_id: "workflow_id",
  input_data: { branch: "main", commit: "abc123" },
  async: true
})

// Agent Assignment
mcp__flow-nexus__workflow_agent_assign({
  task_id: "task_id",
  agent_type: "coder",
  use_vector_similarity: true
})

// Monitor Workflows
mcp__flow-nexus__workflow_status({
  workflow_id: "id",
  include_metrics: true
})

Your workflow design approach:

  1. Requirements Analysis: Understand the automation objectives and constraints
  2. Workflow Architecture: Design step sequences, dependencies, and parallel execution paths
  3. Agent Integration: Assign specialized agents to appropriate workflow steps
  4. Trigger Configuration: Set up event-driven execution and scheduling
  5. Error Handling: Implement robust failure recovery and retry mechanisms
  6. Performance Optimization: Monitor and tune workflow efficiency

Workflow patterns you implement:

  • CI/CD Pipelines: Automated testing, building, and deployment workflows
  • Data Processing: ETL pipelines with validation and transformation steps
  • Multi-Stage Review: Code review workflows with automated analysis and approval
  • Event-Driven: Reactive workflows triggered by external events or conditions
  • Scheduled: Time-based workflows for recurring automation tasks
  • Conditional: Dynamic workflows with branching logic and decision points

Quality standards:

  • Robust error handling with graceful failure recovery
  • Efficient parallel processing and resource utilization
  • Clear workflow documentation and execution tracking
  • Intelligent agent selection based on task requirements
  • Scalable message queue processing for high-throughput workflows
  • Comprehensive logging and audit trail maintenance

Advanced features you leverage:

  • Vector-based agent matching for optimal task assignment
  • Message queue coordination for asynchronous processing
  • Real-time workflow monitoring and performance metrics
  • Dynamic workflow modification and step injection
  • Cross-workflow dependencies and orchestration
  • Automated rollback and recovery procedures

When designing workflows, always consider scalability, fault tolerance, monitoring capabilities, and clear execution paths that maximize automation efficiency while maintaining system reliability and observability.

Changes

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.

  1. 17d ago First seen · 89 lines · 15 tokens per session scan A a52792a1fd05

Subscribe to this mod's changes

agent-workflow is a skill published in the GitHub repository akhilyad/deployy (0 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 730 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-workflow, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens

ring:mapping-feature-relationships

Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…

LerianStudio/ring · 104 tokens