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/discovery/discovery-catalognpx skills add microsoft/discovery --skill discovery-cataloggit clone --depth 1 https://github.com/microsoft/discoveryWrote 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/discovery/discovery-catalog)<a href="https://agentmods.dev/skills/microsoft/discovery/discovery-catalog"><img src="https://agentmods.dev/badge/skills/microsoft/discovery/discovery-catalog.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.00122 | $0.03340 |
| Opus 5 | $0.00061 | $0.01670 |
| Sonnet 5 | $0.00024 | $0.00668 |
| Haiku 4.5 | $0.00012 | $0.00334 |
Grade A, and why
discovery-catalog 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery Catalog
Compatibility
This skill is read-only and runs on Windows, macOS, and Linux through PowerShell. PowerShell 7+ (pwsh) is recommended for consistent table rendering, though the dispatcher also works in Windows PowerShell 5.1 with less polished wrapping.
Overview
Read-only inventory of the Discovery catalog repo. One dispatcher script (scripts/discovery-catalog.ps1) supports list and item-inspection invocations:
| Invocation | What it lists |
|---|---|
discovery-catalog publishers |
Every publisher across agents/ and starter-kits/, with per-publisher agent and starter-kit counts |
discovery-catalog agents |
Every agent in the catalog (one row per agent folder name) |
discovery-catalog agents list-tools |
Every agent plus the tools shipped under each agent's tools/ folder |
discovery-catalog starter-kits |
Every starter kit (one row per kit folder name) |
discovery-catalog <agent-name> describe |
One agent with Name, Publisher, Version, HasTool, Description |
discovery-catalog <starterkit-name> describe |
One starter kit with Name, Publisher, Version, Category, AgentCount, Description |
discovery-catalog <agent-name> list-tools |
One agent with Agent, Publisher, Version, ToolCount, Tools, Description |
Repo layout the script handles
The catalog uses a flat layout — one folder per agent or starter kit directly under the parent directory:
| Asset | Path pattern | Display |
|---|---|---|
| Agent | agents/<agent-name>/ |
<agent-name> |
| Starter kit | starter-kits/<kit-name>/ |
<kit-name> |
| Tool under an agent | agents/<agent>/tools/<tool-name>/ |
<tool-name> |
Inclusion rules:
- An "agent" is any folder containing an
agent.yaml. - A "starter kit" is any folder containing a
kit.json. - Folders without those files (shared helpers, README-only directories) are silently skipped.
- The
agents/tmp/scratch directory used by the deployer skills is always skipped.
Publisher and party come from the asset's metadata, not from the folder location:
What ships with it
1 file 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.
- 4d ago First seen · 286 lines · 122 tokens per session scan A bcec53c1279b
discovery-catalog is a skill published in the GitHub repository microsoft/discovery (235 stars, last pushed today), licensed MIT. It adds 122 tokens to every session and 3,340 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…