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/managed-apps/list-connectorsnpx skills add microsoft/managed-apps --skill list-connectorsgit clone --depth 1 https://github.com/microsoft/managed-appsWhat 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.00036 | $0.00992 |
| Opus 5 | $0.00018 | $0.00496 |
| Sonnet 5 | $0.00007 | $0.00198 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
list-connectors 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 — 96 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.
List Connectors
Two read-only views, depending on what the user is asking:
- What data sources are already bound to this app? →
ms app show --json(inspectsms.config.json). - What connectors are reachable in the active environment? →
ms connector list-actions --connector <id>for a specific connector, or browse the public reference for available api-ids.
Workflow
- Memory Bank → 2. Verify Env → 3. Mode → 4. Run + Present
Step 1: Check Memory Bank
Read memory-bank.md for the app's environment, if recorded. This is for context/verification only (confirming you're working against the expected app/environment) — ms app show --json and ms connector list-actions don't take environment targeting from it and the listing isn't scoped by it.
Step 2: Verify Env
BIN=ms
$BIN auth status # confirm the active UPN
Step 3: Mode
Ask (or infer):
- app: enumerate data sources already wired into the current project (requires
ms.config.jsonin cwd). - connector: list the operations exposed by a specific connector — useful when planning an
/add-*invocation.
Step 4a: App-bound data sources
test -f ms.config.json || { echo "Not in a Microsoft App workspace."; exit 1; }
$BIN app show --json
Parse the response for the data-source list and print a summary:
| Connector | api-id | Type | Name |
|---|---|---|---|
| Dataverse | dataverse |
table | contact |
| SharePoint Online | shared_sharepointonline |
table | Project Milestones |
| Teams | shared_teams |
action | (entire connector) |
Use this to spot drift (e.g., ms.config.json claims a data source that no longer exists in the env).
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 · 96 lines · 36 tokens per session scan A 205024c0bf28
list-connectors is a skill published in the GitHub repository microsoft/managed-apps (5 stars, last pushed 5d ago), licensed MIT. It adds 36 tokens to every session and 992 once invoked, about $0.0002 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-31.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.