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/microsoft/sharepoint-embedded-samples/full-setupnpx skills add microsoft/SharePoint-Embedded-Samples --skill full-setupgit clone --depth 1 https://github.com/microsoft/SharePoint-Embedded-SamplesWhat 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.00058 | $0.00697 |
| Opus 5 | $0.00029 | $0.00349 |
| Sonnet 5 | $0.00012 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
sharepoint-embedded-setup 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SharePoint Embedded — Full Setup
Workflow
Run each script in order. State passes via .env.spe.
Setup Progress:
- [ ] Stage 1 — 01-auth.ps1 -> Azure CLI login
- [ ] Stage 2 — 02-app.ps1 -> Step 2.1: Entra app creation
-> Step 2.2: API permissions
- [ ] Stage 3 — 03-token.ps1 -> Device code auth (user interaction)
- [ ] Stage 4 — 04-container-type.ps1 -> Step 4.1: Container type creation
-> Step 4.2: Tenant registration
- [ ] Stage 5 — 05-container.ps1 -> Step 5.1: Container creation & activation
-> Step 5.2: Proof file + preview link
powershell -File skills/full-setup/01-auth.ps1
powershell -File skills/full-setup/02-app.ps1
powershell -File skills/full-setup/03-token.ps1
powershell -File skills/full-setup/04-container-type.ps1
powershell -File skills/full-setup/05-container.ps1
Output format
Every script ends with a structured block:
=== RESULT ===
Status: OK
Key: Value
View App: https://portal.azure.com/...
=== END ===
Present every line from the RESULT block as a markdown table. Do not drop URL lines.
Stage-specific notes
Stage 3 — 03-token.ps1 opens a browser for interactive sign-in (auth code + PKCE). If the browser cannot open, it falls back to device code flow and prints ACTION REQUIRED: with a URL and code. Use -UseDeviceCode to force device code flow. If .spe-token exists and is valid, this step completes instantly.
Stage 5 — 05-container.ps1 may take 30–60s due to propagation retries (handled automatically). After it finishes, read .env.spe and include PREVIEW_URL in the summary.
Stage 6 — 06-cleanup.ps1 deletes the container type and app. Only run if the user asks. The script prompts for Y/N confirmation before proceeding.
Customization
.\02-app.ps1 -AppDisplayName "Contoso Legal App"
.\04-container-type.ps1 -ContainerTypeName "Legal Cases" -BillingClassification "trial"
.\05-container.ps1 -ContainerName "Sample Case"
What ships with it
9 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.
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 · 71 lines · 58 tokens per session scan A dd3c2488cec0
sharepoint-embedded-setup is a skill published in the GitHub repository microsoft/SharePoint-Embedded-Samples (104 stars, last pushed 8d ago), licensed MIT. It adds 58 tokens to every session and 697 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…