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-studionpx skills add geekfujiwara/CodeAppsDevelopmentStandard --skill copilot-studiogit clone --depth 1 https://github.com/geekfujiwara/CodeAppsDevelopmentStandardWhat 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.00061 | $0.05029 |
| Opus 5 | $0.00030 | $0.02514 |
| Sonnet 5 | $0.00012 | $0.01006 |
| Haiku 4.5 | $0.00006 | $0.00503 |
Grade A, and why
copilot-studio 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.
How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Studio エージェント構築スキル
Copilot Studio エージェントを 生成オーケストレーション（Generative Orchestration）モード一択 で構築する。 外部トリガー・ニュース配信エージェント等の応用パターンまでカバーする統合スキル。
サブリファレンス（必要に応じて参照）
| リファレンス | 内容 |
|---|---|
| 構築リファレンス | 構築手順の詳細・Instructions テンプレート・スクリプトコード |
| 外部公開 WebChat SDK（標準） | 外部公開の標準パターン。BotFramework WebChat SDK で UI フルカスタマイズ・プログラム的メッセージ送信 |
| 外部公開デザインテンプレート（標準 UI） | 標準 UI デザイン：左パネル（カテゴリ別カード＋プロンプトチップス）＋ 右 WebChat パネル（グラデーション枠・AI タイピング Tips） |
| ライトモード・テンプレート集 | ライトモード 5 レイアウト（workspace / minimal / hero-cards / dashboard / sidebar）＋ 全テンプレート標準の**「新しい会話（初期化）」ボタン**（React 再マウント対策 freshWebchatEl()） |
| 外部公開 手動認証（SSO） | Entra ID サインイン必須＋ユーザー権限で Dataverse アクセス（RLS/OBO）。2 アプリ登録・FIC（シークレットレス）・OAuth カードの silent トークン交換 |
| 外部公開 iframe（レガシー・非推奨） | iframe で埋め込む簡易版。UI カスタマイズ不可のため標準では使わない。動作確認・PoC 用のみ |
| 外部トリガー | メール受信・Teams メッセージ・スケジュール等のトリガー追加 |
| トリガーパターン | トリガーの設定パターン集 |
| トラブルシューティング | トリガー関連を中心とした異常系・トラブルシューティング |
| ニュース配信エージェント | RSS + Web検索 + Work IQ MCP によるニュース収集・配信エージェント構築 |
| ニュース配信デプロイガイド | ニュース配信エージェントのデプロイ手順 |
| ニュース配信メールテンプレート | ニュース配信メールの HTML テンプレート |
| トランスクリプト分析 | 会話トランスクリプトの分析パターン（ボット識別・ユーザー識別） |
外部公開 Web サイト開発フロー（必須）
外部公開は WebChat UI（BotFramework WebChat SDK）を標準とする。 iframe 埋め込みは UI カスタマイズができないためレガシー扱いとし、PoC・動作確認以外では使わない。
WebChat UI のデザインは既存のデザインテンプレートを再利用する （新規にゼロからデザインを起こさない）:
- 標準（ダーク UI）: webchat-sdk-design-template.md
- ライトモード / 複数レイアウト: webchat-sdk-light-templates.md
What ships with it
32 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.1 KB
- references/build-reference.md 25 KB
- references/external-web-embed.md 11 KB
- references/market-research-deployment-guide.md 13 KB
- references/market-research-email-template.md 12 KB
- references/market-research-report.md 33 KB
- references/transcript-analytics.md 5.6 KB
- references/trigger-patterns.md 27 KB
- references/trigger.md 41 KB
- references/troubleshooting.md 21 KB
- references/webchat-sdk-design-template.md 20 KB
- references/webchat-sdk-embed.md 28 KB
- references/webchat-sdk-light-templates.md 10.0 KB
- references/webchat-sdk-manual-auth.md 9.4 KB
- scripts/add_fic.py 3.1 KB runs code
- scripts/analyze_bot.py 4.1 KB runs code
- scripts/check_email_trigger_status.py 4.7 KB runs code
- scripts/check_publish.py 432 B runs code
- scripts/deploy_agent.py 31 KB runs code
- scripts/deploy_email_trigger.py 13 KB runs code
- scripts/deploy_news_agent.py 27 KB runs code
- scripts/deploy_news_flow.py 9.3 KB runs code
- scripts/deploy_website.py 8.4 KB runs code
- scripts/fix_email_msgid.py 13 KB runs code
- scripts/fix_email_reply.py 15 KB runs code
- scripts/fix_email_trigger_v2.py 10 KB runs code
- scripts/fix_email_trigger.py 12 KB runs code
- scripts/generate_news_icon.py 5.6 KB runs code
- scripts/set_agent_channels.py 7.0 KB runs code
- scripts/set_agent_security.py 3.4 KB runs code
- scripts/setup_email_trigger.py 8.2 KB runs code
- scripts/setup_webchat_auth.py 13 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 First seen · 330 lines · 61 tokens per session scan A e28b1002a0d0
copilot-studio is a skill published in the GitHub repository geekfujiwara/CodeAppsDevelopmentStandard (59 stars, last pushed 5d ago), licensed MIT. It adds 61 tokens to every session and 5,029 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-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…