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/coworknpx skills add geekfujiwara/CodeAppsDevelopmentStandard --skill coworkgit 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/cowork)<a href="https://agentmods.dev/skills/geekfujiwara/codeappsdevelopmentstandard/cowork"><img src="https://agentmods.dev/badge/skills/geekfujiwara/codeappsdevelopmentstandard/cowork.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.00116 | $0.08619 |
| Opus 5 | $0.00058 | $0.04310 |
| Sonnet 5 | $0.00023 | $0.01724 |
| Haiku 4.5 | $0.00012 | $0.00862 |
Grade A, and why
cowork 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 — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cowork プラグイン開発（Dataverse MCP セット）
目的特化型の Copilot Cowork プラグイン（M365 アプリパッケージ .zip）を作る。
ビジネススキル（SKILL.md）と Dataverse MCP コネクタをセットにし、Entra ID の OAuth 2.0 認可コードフロー認証で
Cowork から Dataverse を直接操作できるようにする。
前提: 利用テナントが Frontier プレビュー に参加していること。 会社環境で Cowork の利用が許可されている場合のみこのスキルを使用してください。利用可否が不明な場合は管理者に確認してください。 異常系・トラブルシュートは references/troubleshooting.md を参照。
パッケージ構成（Skills + remote connector）
<plugin-root>/
├── manifest.json # M365 Unified App Manifest v1.28
├── color.png # 192×192 フルカラーアイコン
├── outline.png # 32×32 アウトラインアイコン
├── build-package.ps1 # .zip 生成（検証付き）
└── skills/
└── <skill-name>/ # kebab-case。フォルダ名 = SKILL.md の name と一致必須
└── SKILL.md # frontmatter(name/description) + ワークフロー本文
前提条件（最初に確認）
- 環境で Microsoft Cowork が許可されていること
python .github/skills/standard/scripts/check_mcp_client.py cowork→ ✅ なら OK。 未許可なら Power Platform 管理センター → 環境 →allowedmcpclientで有効化。 - Frontier 参加（管理者も Copilot → Settings → Frontier に登録）。
- ツール: Python 3（auth_helper.py / アイコン生成）、PowerShell（パッケージビルド）。
スキル同梱スクリプト（再利用）
scripts/ のスクリプトは汎用化されており、どのテナント・環境でも .env（TENANT_ID /
DATAVERSE_URL / PUBLISHER_PREFIX / COWORK_OAUTH_CLIENT_ID）を参照して動作する。
| スクリプト | 用途 |
|---|---|
| scripts/setup_entra_oauth_graph.py | （推奨） Entra OAuth クライアントアプリを Microsoft Graph API 経由で作成。auth_helper.py のキャッシュ済み認証を利用するため追加のデバイスコード認証が不要（Step 3） |
| scripts/setup_entra_oauth.ps1 | （代替）az CLI 経由で同等の処理。az login のデバイスコード認証が必要（Step 3） |
| scripts/register_mcp_client.py | Client ID を Dataverse 許可 MCP クライアント（allowedmcpclients）に登録・有効化・確認（Step 4） |
| scripts/diagnose_cowork_connector.py | アプリ登録・admin consent・allowedmcpclients の3層をまとめて診断（Step 4→5 の間で実行推奨） |
| scripts/build_agent_package.ps1 | .env の COWORK_OAUTH_REGISTRATION_ID（引用符付きでも可）を manifest.json のプレースホルダーに注入し、必須ファイルを検証して .zip を生成（Step 7） |
What ships with it
7 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/troubleshooting.md 24 KB
- scripts/build_agent_package.ps1 6.1 KB runs code
- scripts/diagnose_cowork_connector.py 9.0 KB runs code
- scripts/diagnose_dlp_block.py 3.3 KB runs code
- scripts/register_mcp_client.py 6.3 KB runs code
- scripts/setup_entra_oauth_graph.py 11 KB runs code
- scripts/setup_entra_oauth.ps1 4.9 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 · 447 lines · 116 tokens per session scan A 7bdd366939b7
cowork is a skill published in the GitHub repository geekfujiwara/CodeAppsDevelopmentStandard (60 stars, last pushed today), licensed MIT. It adds 116 tokens to every session and 8,619 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…