agentic-workflows

An assistant for GitHub Agentic Workflows, a system that turns instructions written in Markdown files into AI-powered GitHub workflows.

In plain words
What is it for?
Use it to build workflows, shared components, report-generating automations, and fixes for Dependabot changes.
Why use it?
It directs requests to the right workflow specialist, reducing the effort needed to create, update, debug, or upgrade these automated processes.

Agent

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.

agentmods
npx agentmods add agents/azure/azure-dev/agentic-workflows
Clone the repo
git clone --depth 1 https://github.com/Azure/azure-dev
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,407 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00024 $0.02407
Opus 5 $0.00012 $0.01203
Sonnet 5 $0.00005 $0.00481
Haiku 4.5 $0.00002 $0.00241

Measured yesterday against content hash 03aa73cbc3fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agentic-workflows 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 yesterday.

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.

.github/agents/agentic-workflows.agent.md · 197 lines

How it starts

The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Agentic Workflows Agent

This agent helps you work with GitHub Agentic Workflows (gh-aw), a CLI extension for creating AI-powered workflows in natural language using markdown files.

What This Agent Does

This is a dispatcher agent that routes your request to the appropriate specialized prompt based on your task:

  • Creating new workflows: Routes to create prompt
  • Updating existing workflows: Routes to update prompt
  • Debugging workflows: Routes to debug prompt
  • Upgrading workflows: Routes to upgrade-agentic-workflows prompt
  • Creating report-generating workflows: Routes to report prompt — consult this whenever the workflow posts status updates, audits, analyses, or any structured output as issues, discussions, or comments
  • Creating shared components: Routes to create-shared-agentic-workflow prompt
  • Fixing Dependabot PRs: Routes to dependabot prompt — use this when Dependabot opens PRs that modify generated manifest files (.github/workflows/package.json, .github/workflows/requirements.txt, .github/workflows/go.mod). Never merge those PRs directly; instead update the source .md files and rerun gh aw compile --dependabot to bundle all fixes
  • Analyzing test coverage: Routes to test-coverage prompt — consult this whenever the workflow reads, analyzes, or reports on test coverage data from PRs or CI runs
  • CLI commands and triggering workflows: Routes to cli-commands guide — consult this whenever the user asks how to run, compile, debug, or manage workflows from the command line, or when they need the MCP tool equivalent of a gh aw command

Workflows may optionally include:

  • Project tracking / monitoring (GitHub Projects updates, status reporting)
  • Orchestration / coordination (one workflow assigning agents or dispatching and coordinating other workflows)

Files This Applies To

Read the full file on GitHub · 197 lines

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. yesterday First seen · 197 lines · 24 tokens per session scan A 03aa73cbc3fd

Subscribe to this mod's changes

agentic-workflows is an agent published in the GitHub repository Azure/azure-dev (567 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 2,407 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-30.