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 skills add itallstartedwithaidea/agent-skills --skill workflow-orchestrationgit clone --depth 1 https://github.com/itallstartedwithaidea/agent-skillsWrote 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/skills/itallstartedwithaidea/agent-skills/workflow-orchestration)<a href="https://agentmods.dev/skills/itallstartedwithaidea/agent-skills/workflow-orchestration"><img src="https://agentmods.dev/badge/skills/itallstartedwithaidea/agent-skills/workflow-orchestration.svg" alt="Measured on agentmods" 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.00031 | $0.01540 |
| Opus 5 | $0.00015 | $0.00770 |
| Sonnet 5 | $0.00006 | $0.00308 |
| Haiku 4.5 | $0.00003 | $0.00154 |
Grade A, and why
workflow-orchestration 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 7d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Orchestration
Part of Agent Skills™ by googleadsagent.ai™
Description
Workflow Orchestration provides a visual AI flow-building framework with MCP plugin support, conditional branching, parallel execution, and error recovery. The agent designs and implements multi-step workflows that chain AI operations, data transformations, and external service calls into reliable, repeatable automation pipelines.
Individual AI calls are useful; orchestrated workflows are transformative. A content pipeline that drafts text, fact-checks claims, generates images, formats for multiple platforms, and schedules publication—all triggered by a single input—replaces hours of manual coordination. This skill encodes the patterns for building such workflows: DAG-based execution, conditional routing, retry logic, and human-in-the-loop checkpoints.
The MCP (Model Context Protocol) plugin system extends workflows with external capabilities: database queries, file operations, API calls, and browser automation. Each MCP tool becomes a reusable node in the workflow graph, enabling agents to interact with any system that exposes an MCP interface. Workflows compose these nodes into complex automations without custom integration code.
Use When
- Building multi-step AI automation pipelines
- Chaining LLM calls with data transformations and API integrations
- Implementing conditional logic in AI workflows (if/else, switch)
- Adding human-in-the-loop approval steps to automated processes
- Integrating MCP tools into repeatable workflows
- Orchestrating parallel AI tasks with dependency management
How It Works
graph TD
A[Trigger: Manual / Schedule / Webhook] --> B[Node 1: Input Parser]
B --> C{Conditional Router}
C -->|Type A| D[Node 2a: LLM Analysis]
C -->|Type B| E[Node 2b: Database Query via MCP]
D --> F[Node 3: Parallel Execution]
E --> F
F --> G[Node 3a: Image Generation]
F --> H[Node 3b: Content Formatting]
G --> I[Node 4: Human Review Checkpoint]
H --> I
I -->|Approved| J[Node 5: Publish via MCP]
I -->|Rejected| K[Node 5: Return to Step 2]
J --> L[Node 6: Log + Notify]
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.
- 7d ago First seen · 167 lines · 31 tokens per session scan A f395bf4fba11
workflow-orchestration is a skill published in the GitHub repository itallstartedwithaidea/agent-skills (37 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 1,540 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
progress-photo-analyzer
Analyze construction site photos to track progress, detect safety issues, and compare against BIM models using computer vision.