Microsoft Managed Apps is a project for building custom web applications with React, TypeScript, and Vite, and it provides Microsoft's official templates and development tooling. Developers use its SDK, CLI, and Vite plugin to create and manage these applications. Its catalogue add-ons help AI coding agents build Microsoft Managed Apps.
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 microsoft/managed-apps --skill deploygit clone --depth 1 https://github.com/microsoft/managed-appsWrote 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/microsoft/managed-apps/deploy)<a href="https://agentmods.dev/skills/microsoft/managed-apps/deploy"><img src="https://agentmods.dev/badge/skills/microsoft/managed-apps/deploy/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/microsoft/managed-apps/deploy"><img src="https://agentmods.dev/badge/skills/microsoft/managed-apps/deploy.svg" alt="Reviewed on agentmods" width="80" 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.00032 | $0.01996 |
| Opus 5.5 | $0.00013 | $0.00798 |
| Sonnet 5.5 | $0.00006 | $0.00399 |
| Haiku 4.5 | $0.00003 | $0.00200 |
Grade A, and why
deploy 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 5d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📋 Shared Instructions: shared-instructions.md — Cross-cutting concerns. Always confirm before deploy.
Deploy
Builds and deploys the app in the current directory.
Before any deploy, sync source control first: stage all changes, create a commit, and push to remote.
Workflow
- Memory Bank → 2. Verify Project + Env → 3. Pick Path → 4. Shared Connection Policy Preflight → 5. Build Verification → 6. Git Sync (Add + Commit + Push) → 7. Confirm + Deploy → 8. Update Memory Bank
Step 1: Check Memory Bank
Read memory-bank.md for app slug, GUID, and environment.
Step 2: Verify Project + Env
test -f ms.config.json || { echo "Not in a Microsoft App workspace."; exit 1; }
git rev-parse --is-inside-work-tree >/dev/null 2>&1 || { echo "Not in a git repository."; exit 1; }
BIN=ms
$BIN auth status # must report the expected UPN
If auth is stale or the wrong account, stop and have the user run $BIN auth login.
Step 3: Pick a Deploy Path
Ask the user which path:
| Path | When |
|---|---|
Standard deploy (ms app deploy [--commit <sha>]) |
Default. Use for normal release flow. --commit defaults to git rev-parse HEAD. |
Traced deploy (ms app build + ms app build-status + ms app deploy) |
Use when the user needs explicit build-id tracking before deploy. |
ms app build -c <sha> + ms app build-status -o <build-id> is a third (older) two-step variant for the cloud-built path. The build subcommand is marked deprecated in the CLI source but still works; use it only when the user wants an explicit build-id to track. Otherwise, ms app deploy is the single-step replacement.
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.
- 5d ago Changed · -2 lines e103792b6e94
- 1mo ago Changed · +46 lines 33d8a6fb1559
- 2mo ago Changed · -1 lines 81810f458e67
- 2mo ago First seen · 148 lines · 32 tokens per session scan A 37fdbe8f2a2a
deploy is a skill published in the GitHub repository microsoft/managed-apps (36 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 1,996 once invoked, about $0.0001 per session on Opus 5.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-31.
deploy compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| deploymicrosoft/managed-apps | Skill | 36 | 3d ago | MIT | A | 32 | Claude Code |
| gke-compute-classesgoogle/skills | Skill | 24k | yesterday | Apache-2.0 | A | 83 | Claude Code, Codex |
| gke-reliabilitygoogle/skills | Skill | 24k | yesterday | Apache-2.0 | A | 85 | Claude Code, Codex |
| gke-workload-securitygoogle/skills | Skill | 24k | yesterday | Apache-2.0 | A | 171 | Claude Code, Codex |
| cloud-architectJeffallan/claude-skills | Skill | 12k | 9d ago | MIT | A | 71 | Claude Code |
| nemo-automodel-launcher-configNVIDIA/skills | Skill | 3.9k | yesterday | Apache-2.0 | A | 30 | Claude Code |
| azure-mgmt-botservice-dotnetmicrosoft/skills | Skill | 3.2k | 2d ago | MIT | A | 78 | Claude Code |