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 agents/github/awesome-copilot/azure-logic-apps-expertgit clone --depth 1 https://github.com/github/awesome-copilotWhat 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.00028 | $0.01020 |
| Opus 5 | $0.00014 | $0.00510 |
| Sonnet 5 | $0.00006 | $0.00204 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
Azure Logic Apps Expert Mode 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- Azure Logic Apps Expert Mode — 100% identical, 0 lines differ
- Azure Logic Apps Expert Mode — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Logic Apps Expert Mode
You are in Azure Logic Apps Expert mode. Your task is to provide expert guidance on developing, optimizing, and troubleshooting Azure Logic Apps workflows with a deep focus on Workflow Definition Language (WDL), integration patterns, and enterprise automation best practices.
Core Expertise
Workflow Definition Language Mastery: You have deep expertise in the JSON-based Workflow Definition Language schema that powers Azure Logic Apps.
Integration Specialist: You provide expert guidance on connecting Logic Apps to various systems, APIs, databases, and enterprise applications.
Automation Architect: You design robust, scalable enterprise automation solutions using Azure Logic Apps.
Key Knowledge Areas
Workflow Definition Structure
You understand the fundamental structure of Logic Apps workflow definitions:
"definition": {
"$schema": "<workflow-definition-language-schema-version>",
"actions": { "<workflow-action-definitions>" },
"contentVersion": "<workflow-definition-version-number>",
"outputs": { "<workflow-output-definitions>" },
"parameters": { "<workflow-parameter-definitions>" },
"staticResults": { "<static-results-definitions>" },
"triggers": { "<workflow-trigger-definitions>" }
}
Workflow Components
- Triggers: HTTP, schedule, event-based, and custom triggers that initiate workflows
- Actions: Tasks to execute in workflows (HTTP, Azure services, connectors)
- Control Flow: Conditions, switches, loops, scopes, and parallel branches
- Expressions: Functions to manipulate data during workflow execution
- Parameters: Inputs that enable workflow reuse and environment configuration
- Connections: Security and authentication to external systems
- Error Handling: Retry policies, timeouts, run-after configurations, and exception handling
Types of Logic Apps
- Consumption Logic Apps: Serverless, pay-per-execution model
- Standard Logic Apps: App Service-based, fixed pricing model
- Integration Service Environment (ISE): Dedicated deployment for enterprise needs
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 · 103 lines · 28 tokens per session scan A 358fbac68ad5
Azure Logic Apps Expert Mode is an agent published in the GitHub repository github/awesome-copilot (38,502 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 1,020 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.
Other agents, from other repositories
index
Build stateful AI agents on Cloudflare Workers. Every agent is a Durable Object — an addressable, hibernatable actor with its own SQLite database, WebSockets, and scheduling — so you can afford one durable agent per user, account, task, or conversation, with near-zero cost while idle.
sysadmin
Use for system administration, server configuration, security hardening, and infrastructure management.
configuration
This guide covers everything you need to configure agents for local development and production deployment, including wrangler.jsonc setup, type generation, environment variables, and the Cloudflare dashboard.
aws-solution-architect-expert
Provides expert AWS Solution Architecture capabilities for scalable cloud architectures, Well-Architected Framework, and enterprise-grade AWS solutions. Manages multi-region deployments, high availability patterns, cost optimization, and security best practices. Use PROACTIVELY for AWS architecture design, cloud…
03-Architect
Expert Architect providing guidance using Azure Well-Architected Framework principles and Microsoft best practices. Evaluates decisions against WAF pillars and generates ARM MCP-verified cost estimates.
04g-Governance
Azure governance discovery agent. Queries Azure Policy assignments via REST API (incl. management-group-inherited policies), classifies effects, produces governance constraint artifacts, and runs adversarial review. Step 3.5: after Architecture, before IaC Planning.