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/copilot-studio-v2npx skills add geekfujiwara/CodeAppsDevelopmentStandard --skill copilot-studio-v2git 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/copilot-studio-v2)<a href="https://agentmods.dev/skills/geekfujiwara/codeappsdevelopmentstandard/copilot-studio-v2"><img src="https://agentmods.dev/badge/skills/geekfujiwara/codeappsdevelopmentstandard/copilot-studio-v2.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 | $0.00124 | $0.05318 |
| Opus 5 | $0.00062 | $0.02659 |
| Sonnet 5 | $0.00025 | $0.01064 |
| Haiku 4.5 | $0.00012 | $0.00532 |
Grade A, and why
copilot-studio-v2 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 4d 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Studio v2(新アーキテクチャ)エージェント構築スキル
Copilot Studio の 「全く新しいアーキテクチャ」(cliagent テンプレート) エージェントを
Dataverse Web API だけで完全自動構築 する。
v1(旧)スキルとの最大の違い
| 観点 | v1(copilot-studio スキル / 旧アーキ) |
v2(本スキル / 新アーキ cliagent) |
|---|---|---|
| Bot 作成 | ❌ API 不可。Copilot Studio UI で手動作成必須 | ✅ POST /bots で API 作成可能。UI 不要・完全自動 |
| 設定の保存先 | GPT コンポーネント(componenttype=15)+ PVA ダブル改行 YAML | bots.configuration の BotConfiguration JSON にインライン |
| recognizer | (クラシック PVA) | CLICopilotRecognizer |
| モデル指定 | GPT data の aISettings.model.modelNameHint |
agentSettings.model.series(例 claude-opus-5) |
| Instructions | GPT data YAML(ダブル改行フォーマット注意) | agentSettings.instructions.segments[].value(プレーン文字列) |
| メモリ | (個別設定) | agentSettings.enableMemory: true |
| スキル | (ナレッジ/トピック) | フラット Python スキルバンドル(type=9 + type=14 子ファイル) |
| 自動化適性 | △ UI 介在が必要 | ◎ エンドツーエンドでスクリプト完結 |
このスキルを選ぶ理由: Bot 作成からスキル添付まで 人手の UI 操作ゼロ で構築できる。 CI/再現構築・量産・プログラム的な改変に向く。
いつ v2 を使うか(architecture スキルでの分岐)
architecture スキルの Copilot Studio 選定時に、ユーザーへ v2 / v1 のどちらで作るか を確認する。
判断の起点は「他サービスと連携して使うか、単独で使うか」:
- 連携利用(Code Apps / Web サイト / 他システムから呼び出す)→ v1 を推奨。 v2(cliagent)は Code Apps から呼び出せず・Web サイトにも埋め込めない致命的制約があるため。
- 単独利用(Teams / Copilot Studio 単体の対話のみ)→ v2 を推奨(UI 操作なしで自動構築できるため)。
致命的制約: v2 のエージェントは Code Apps の
ExecuteCopilotAsyncV2連携や WebChat SDK での 外部公開に対応しない。これらのシナリオでは必ず v1 を選ぶ。
| v2(新アーキ)が向く=単独利用 | v1(旧アーキ)が向く=連携利用 |
|---|---|
| Teams 等で単独利用し、外部から呼び出さない | Code Apps / Web サイト / 他システムから呼び出す(v2 不可) |
| UI 操作なしで自動構築したい | 外部公開(Web 埋め込み・WebChat SDK)・トリガー・ニュース配信の既存資産を流用したい |
| フラット Python スキルでツール挙動を実装したい | conversationStarters / 会話の開始 / クイック返信を細かく作り込みたい |
| 再現構築・量産・プログラム的改変 | クラシックなナレッジ/トピック中心の構成 |
構築フロー(完全自動)
1. .env 準備(DATAVERSE_URL / TENANT_ID / 任意で SOLUTION_NAME・PUBLISHER_PREFIX)
2. 設計提示 → ユーザー承認(名前・Instructions・モデル・スキル・アイコン・MCP 構成)
- ファイル出力を伴うスキルを添付する場合は、Instructions に
「ファイルを出力する際は毎回異なるファイル名にする」旨を含める(同名だと UI でダウンロード不可)
- 初期メッセージ(greeting)と推奨プロンプトを agent/prompts.json に用意し、AGENT_PROMPTS_FILE で指定する
3. scripts/create_agent.py … cliagent Bot を API 作成 + プロビジョニング待ち
(AGENT_PROMPTS_FILE があれば初期メッセージ・推奨プロンプトもここで設定)
4. scripts/set_icon.py … アイコン登録(240 / Teams color 192 / outline 32)
5. scripts/set_app_details.py … Edit details(説明文・開発元・リンク・Teams 設定・M365 有効化)
6. scripts/attach_skill.py … フラット Python スキルを添付(type=9 + type=14)
7. scripts/publish_agent.py … PvaPublish で公開
8. scripts/verify_agent.py … 構造検証(filedata 実体ダウンロード確認)
9. pac copilot list … Published / Active / Provisioned を確認
10. UI で Build > Model の表示を確認 … 「廃止されたモデル」なら scripts/set_model.py で修正し再公開
11. UI で MCP サーバーを追加(Dataverse / Work IQ 等)… ★手動作業(後述)
12. Preview で動作テスト(ユーザー)
What ships with it
22 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 4.3 KB
- references/app-details.md 6.8 KB
- references/flat-python-skill.md 5.5 KB
- references/icon-and-publish.md 2.8 KB
- references/mcp-servers.md 6.0 KB
- references/model-series.md 3.1 KB
- references/new-architecture.md 4.5 KB
- references/skill-bundle-structure.md 4.0 KB
- references/troubleshooting.md 3.7 KB
- scripts/analyze_agent.py 3.2 KB runs code
- scripts/attach_skill.py 5.9 KB runs code
- scripts/create_agent.py 6.3 KB runs code
- scripts/deploy_agent.py 3.5 KB runs code
- scripts/publish_agent.py 2.8 KB runs code
- scripts/set_app_details.py 18 KB runs code
- scripts/set_icon.py 5.8 KB runs code
- scripts/set_instructions.py 3.7 KB runs code
- scripts/set_model.py 4.0 KB runs code
- scripts/set_prompts.py 6.4 KB runs code
- scripts/update_agent.py 5.9 KB runs code
- scripts/verify_agent.py 2.1 KB runs code
- scripts/verify_config.py 1.8 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.
- 4d ago First seen · 309 lines · 124 tokens per session scan A ea44f519546b
copilot-studio-v2 is a skill published in the GitHub repository geekfujiwara/CodeAppsDevelopmentStandard (60 stars, last pushed today), licensed MIT. It adds 124 tokens to every session and 5,318 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…