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 khalilbenaz/claude-skills-collection --skill power-automate-designergit clone --depth 1 https://github.com/khalilbenaz/claude-skills-collectionWrote 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/khalilbenaz/claude-skills-collection/power-automate-designer)<a href="https://agentmods.dev/skills/khalilbenaz/claude-skills-collection/power-automate-designer"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/power-automate-designer/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/skills/khalilbenaz/claude-skills-collection/power-automate-designer"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/power-automate-designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00070 | $0.02096 |
| Opus 5 | $0.00035 | $0.01048 |
| Sonnet 5 | $0.00014 | $0.00419 |
| Haiku 4.5 | $0.00007 | $0.00210 |
Grade A, and why
power-automate-designer 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 9d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Power Automate Designer
Workflow
1. Analyser le besoin d'automatisation
Cartographier le processus AVANT d'ouvrir Power Automate :
- Déclencheur : qu'est-ce qui lance le flow ? (email reçu, fichier déposé, formulaire soumis, heure planifiée, appel HTTP)
- Données d'entrée : quelles informations sont disponibles au déclenchement ?
- Étapes : quelles actions manuelles remplace-t-on ?
- Sorties : notifications, fichiers créés, enregistrements mis à jour, appels API
Critère go/no-go : si le processus contient des décisions subjectives ou nécessite une interface graphique legacy non automatisable par API, préférer un Business Process Flow ou un Desktop Flow.
2. Choisir le type de flow
| Type | Cas d'usage | Limite clé |
|---|---|---|
| Cloud Flow automatisé | Trigger event-driven (email, SharePoint, Teams) | Dépend de la disponibilité du connecteur |
| Cloud Flow instantané | Déclenché manuellement ou via bouton Teams/mobile | Nécessite une interaction humaine |
| Cloud Flow planifié | Batch quotidien/hebdomadaire, rapports récurrents | Pas de réactivité aux événements |
| Desktop Flow (RPA) | Applications sans API (ERP legacy, interfaces Windows) | Machine cible doit être active + Power Automate Desktop installé |
| Business Process Flow | Guidage étape par étape (onboarding, validation multi-niveaux) | Uniquement avec Dataverse |
3. Configurer les connecteurs
Connecteurs standard courants : SharePoint, Outlook, Teams, Excel Online, Forms, Planner, OneDrive, Dataverse.
Connecteur personnalisé (API interne ou tierce non couverte) :
# Exemple de définition OpenAPI minimale pour connecteur custom
openapi: "2.0"
info:
title: Mon API Interne
version: "1.0"
host: api.monentreprise.com
basePath: /v1
schemes: [https]
paths:
/orders/{id}:
get:
operationId: GetOrder
parameters:
- name: id
in: path
required: true
type: string
responses:
200:
description: OK
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.
- 9d ago First seen · 195 lines · 70 tokens per session scan A a7f16e4860d3
power-automate-designer is a skill published in the GitHub repository khalilbenaz/claude-skills-collection (22 stars, last pushed 19d ago), licensed MIT. It adds 70 tokens to every session and 2,096 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
instinct-review
Reviews/promotes/removes instincts from .claude/instincts/.md. Triggers: instinct review, curate instincts, manage instincts, promote instinct.
repeat
Runs prompt/slash command on recurring interval until done or limit. Triggers: repeat, recurring task, poll status, run every N minutes, interval.
night-watch
Autonomous maintenance (dep updates, dead code, small refactors) in isolated branch, off-hours. Triggers: night watch, autonomous maintenance, dep updates.
briefing
Executive daily briefing aggregating reports from all agents into decision-focused summary. Triggers: briefing, daily summary, status across system, executive update.
work-autonomous
Abbruchbedingung für autonome Loops: So weit wie möglich selbständig weiterarbeiten UND einen Loop erst beenden, wenn belegt ist, dass keine autonom ausführbare Aufgabe mehr vorliegt. Der bloße Eindruck "nichts mehr zu tun" reicht NICHT — er löst eine vierstufige Prüfkette aus (think/decide, CONTROL/DECISIONS…
rotation-check
Standard-Gerüst für rotierende Pipeline-Checks: Pro Lauf genau ein Ziel aus einer Menge (Projekte, Ordner, Repos) wählen — bevorzugt das am längsten ungeprüfte —, den Check durchführen, Ergebnis in einer Check-Registry und einem Verlaufslog festhalten. Nutze diesen Skill, wenn ein wiederkehrender Check über viele…