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 skills/geekfujiwara/codeappsdevelopmentstandard/power-automatenpx skills add geekfujiwara/CodeAppsDevelopmentStandard --skill power-automategit clone --depth 1 https://github.com/geekfujiwara/CodeAppsDevelopmentStandardWrote 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/geekfujiwara/codeappsdevelopmentstandard/power-automate)<a href="https://agentmods.dev/skills/geekfujiwara/codeappsdevelopmentstandard/power-automate"><img src="https://agentmods.dev/badge/skills/geekfujiwara/codeappsdevelopmentstandard/power-automate.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.00085 | $0.06997 |
| Opus 5 | $0.00043 | $0.03499 |
| Sonnet 5 | $0.00017 | $0.01399 |
| Haiku 4.5 | $0.00009 | $0.00700 |
Grade A, and why
power-automate scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
r = requests.get( How it starts
The opening of the file, as written. The whole thing — 605 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Power Automate クラウドフロー構築スキル
クラウドフロー開発は Flow agent MCP SERVER（FlowAgent）を第一選択とする。 MCP が利用できない環境では Dataverse Web API（workflow テーブル）経由のフォールバックを使う。
推奨: Flow agent MCP SERVER を使う（第一選択）
FlowAgent MCP SERVER を使うと、VS Code の GitHub Copilot Chat（エージェントモード）からフローを自然言語で構築・編集・デバッグできる。
| 比較項目 | Flow agent MCP（推奨） | Dataverse Web API（フォールバック） |
|---|---|---|
| フロー作成 | 自然言語で指示するだけ | Python スクリプトを手書き |
| 編集 | アクション単位のサージカル編集 | 定義 JSON を全置換 |
| デバッグ | 失敗ランを自律診断 | ログを手動確認 |
| 接続解決 | 自動検索・自動紐づけ | PowerApps API + 手動確認 |
| セットアップ | スクリプト 1 本で完結 | Python 環境 + 複数スコープのトークン |
★ FlowAgent MCP サーバー本体（
server/mcp.mjs）は Claude Code / GitHub Copilot CLI 用の プラグインマーケットプレイス（microsoft/power-platform-skills）で配布されているが、 VS Code の GitHub Copilot Chat は/plugin marketplace addコマンドや Claude 形式の.mcp.json（mcpServersキー）を解釈できない。VS Code は独自の MCP クライアントを持ち、 ワークスペース直下の.vscode/mcp.json（serversキー +type: "stdio"）を読む。 そのため本スキルではmicrosoft/power-platform-skillsリポジトリを git スパースチェックアウトで 直接取得し、VS Code 形式で登録する（プラグインマーケットプレイスは経由しない）。
1. 前提
- Node.js 20+（FlowAgent v3.0.0 以降は MCP SDK v2 のため Node.js 18 では起動できない）
- git（
microsoft/power-platform-skillsのplugins/power-automateを取得するために使用） - Azure CLI（
az login— MCP サーバー自身の認証に必要。auth_helper.pyとは別の資格情報ストア）
2. 認証 + .vscode/mcp.json 生成（auth_helper を使用）
.env に DATAVERSE_URL / SOLUTION_NAME を設定してからスクリプトを実行する。
スクリプトが行うこと:
| 処理 | 内容 |
|---|---|
| Node.js 確認 | 20+ でなければ中断 |
| az login 確認 | az account list で対象テナントの既存キャッシュを確認 → あれば az account set のみ（対話不要）。無い場合のみ案内を表示 |
| auth_helper 認証 | Dataverse / Flow API トークンを取得・キャッシュ（Python スクリプト用） |
| プラグイン取得 | microsoft/power-platform-skills を git スパースチェックアウトで ~/.power-platform-skills に取得（マシン全体で共有・自動更新） |
| .vscode/mcp.json 生成 | 既存エントリを保持しつつ FlowAgent を追記（VS Code 形式） |
python .github/skills/power-automate/scripts/setup_flow_mcp.py
内容確認だけしたい場合:
python .github/skills/power-automate/scripts/setup_flow_mcp.py --dry-run
.vscode/mcp.jsonは環境依存パスを含むためコミットしない（.vscode/*は標準.gitignoreで除外済み）。
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/.env.example 2.1 KB
- references/flow-agent-mcp.md 16 KB
- references/notification-templates.md 20 KB
- references/trigger-action-patterns.md 36 KB
- references/troubleshooting.md 4.6 KB
- scripts/add_flow_to_solution.py 2.4 KB runs code
- scripts/deploy_flow_create_notify.py 39 KB runs code
- scripts/deploy_flow_sp_record.py 21 KB runs code
- scripts/deploy_flow_sp_teams.py 25 KB runs code
- scripts/deploy_flow.py 24 KB runs code
- scripts/setup_flow_mcp.py 20 KB runs code
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 Changed e18d932a5c00
- 6d ago First seen · 605 lines · 85 tokens per session scan A 1a6edbd70584
power-automate is a skill published in the GitHub repository geekfujiwara/CodeAppsDevelopmentStandard (62 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 6,997 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…