Microsoft Discovery is an extensible platform for scientific research and research-and-development workflows that combines agent orchestration, reasoning, graph-based knowledge, and high-performance computing. Researchers, partners, and product users use its Azure enterprise platform or local Windows app to explore and build research workflows. The catalogue entries provide skills and instructions for working with the Discovery community and platform.
Borrowing it
Nothing to install: this file belongs to microsoft/discovery. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/discovery/main/.github/skills/discovery-services-agent-deployer/SKILL.mdgit 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-services-agent-deployer)<a href="https://agentmods.dev/skills/microsoft/discovery/discovery-services-agent-deployer"><img src="https://agentmods.dev/badge/skills/microsoft/discovery/discovery-services-agent-deployer/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/discovery/discovery-services-agent-deployer"><img src="https://agentmods.dev/badge/skills/microsoft/discovery/discovery-services-agent-deployer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Tool Misuse · line 51 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Tool Misuse · line 87 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Excessive Agency · line 66 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00099 | $0.03338 |
| Opus 5.5 | $0.00040 | $0.01335 |
| Sonnet 5.5 | $0.00020 | $0.00668 |
| Haiku 4.5 | $0.00010 | $0.00334 |
Grade A, and why
discovery-services-agent-deployer 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 1mo 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery Agent Deployer
Compatibility
Runs on Windows, macOS, and Linux through PowerShell 7+ (pwsh). Requires git, python with pip, and Azure CLI (az). Docker is optional because the runner can use Azure Container Registry Tasks when local Docker is unavailable.
What this skill does
Deploy one or more Discovery catalog agents from this repository with a single deterministic runner:
pwsh -NoProfile -ExecutionPolicy Bypass -File .github/skills/discovery-services-agent-deployer/scripts/deploy-discovery-agent.ps1 <agent-name>
The single PowerShell script discovers the agent folder, selects its tool folder when present, builds and pushes the image, creates or updates the Microsoft.Discovery/tools resource, patches a run-local copy of agent.yaml, deploys the agent, validates it with a temporary investigation, and prints a final summary. If the agent has no tool, it skips build and deploy-tool and continues with agent deployment. It persists stage status to stage-todos.json in the run directory so the invoking assistant can keep native Copilot task tracking in sync without duplicating progress logs.
When to use
Use this skill for requests like:
- "/discovery-services-agent-deployer
chembl" - "/discovery-services-agent-deployer
chemblaizynthfinder" - "Deploy the
aizynthfinderagent" - "Build and publish the tool image for this Discovery agent"
- "Create the Discovery tool resource from this agent's Dockerfile and tool.yaml"
- "Resume the failed deployment in this run folder"
- "Show me what would be deployed for this agent before running it"
If the user only wants inventory, use the discovery-catalog skill instead.
Customer inputs
The happy path needs only the agent name. Optional parameters reduce rework or make automation explicit:
| Parameter | Purpose |
|---|---|
<agent-name> [agent-name...] or -AgentName <name>[,<name>...] |
Agent folder name under agents/. Positional names are preferred for slash-style use such as /discovery-services-agent-deployer chembl aizynthfinder. Required unless resuming. |
-PublisherName <name> |
Deprecated. Tolerated for backwards compatibility but ignored — agents live in the flat agents/<agent-name>/ layout with no publisher folder. The deployer prints a one-line deprecation notice when the flag is supplied. |
-BuildMode auto|remote|local |
Defaults to auto; if input is required, ask the customer for remote or local. Do not store build mode in config.json. |
-Resume <RunDir> |
Continues from a prior checkpointed run. |
-Stage init|build|deploy-tool|deploy-agent|validate|summary|stop |
Runs exactly one stage, allowing Copilot to update native TODOs between terminal commands. |
-RunDir <RunDir> |
Required with -Stage after init. |
-ConfirmSupercomputerNodepools |
Run-scoped confirmation that the customer chose Proceed for the current run's tool/SKU plan. Do not store this in config.json. |
-ValidationPrompt <prompt> |
Run-scoped validation prompt generated by Copilot from the deployed agent/tool context. Overrides config testPrompt for this run. |
-SkipValidation |
Deploys without the post-deploy investigation test. |
-WhatIfPlan |
Prints repo discovery and planned stages without Azure calls. |
What ships with it
5 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.
- 1mo ago First seen · 175 lines · 99 tokens per session scan A cbbe4dcc4a73
discovery-services-agent-deployer is a skill published in the GitHub repository microsoft/discovery (267 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 3,338 once invoked, about $0.0004 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-30.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".