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 aiappsgbb/awesome-gbb --skill hosted_agent_deploy_expertgit clone --depth 1 https://github.com/aiappsgbb/awesome-gbbWrote 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/aiappsgbb/awesome-gbb/hosted_agent_deploy_expert)<a href="https://agentmods.dev/skills/aiappsgbb/awesome-gbb/hosted_agent_deploy_expert"><img src="https://agentmods.dev/badge/skills/aiappsgbb/awesome-gbb/hosted_agent_deploy_expert.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.1 | $0.00051 | $0.00746 |
| Opus 5 | $0.00026 | $0.00373 |
| Sonnet 5 | $0.00010 | $0.00149 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
hosted_agent_deploy_expert scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `Request body must be a JSON object with a non-empty input string` | `azd ai agent invoke` envelope bug | ghcp-hosted-agents KI-001 (use `curl` with `{"input":"..."}`) | How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hosted_agent_deploy_expert
When to use
- A user reports a failed
azd up,azd ai agent deploy, orazd deployfor a Foundry hosted agent - A scheduled task flags failed deployments in the monitored Foundry project
- A hosted agent starts but the first
/invokereturns errors
Investigation flow
-
Identify the failed deploy — agent name, approximate time, which command the user ran.
-
Check the Foundry project's deployments:
az ml online-deployment list \ --workspace-name <project> --resource-group <rg> \ --output tableCapture
instanceName,provisioningState,failureReasonfor each failed deployment. -
Pull container logs from App Insights for the failure window:
traces | where timestamp > ago(1h) | where cloud_RoleName == "<agent-name>" | where severityLevel >= 2 | project timestamp, message, severityLevel, customDimensions | top 50 by timestamp desc -
Classify by pattern:
Pattern in logs Root cause KI Authentication failed with provider ... (HTTP 401)Foundry User missing at account scope foundry-hosted-agents KI-001 cannot import name 'AzureOpenAIChatClient' from 'agent_framework.azure'MAF SDK 1.4.0 breaking change foundry-hosted-agents KI-002 (replace with OpenAIChatClientfromagent_framework.openai)SkillsProvider object has no attribute 'skill_paths'MAF API change foundry-hosted-agents KI-003 (use SkillsProvider.from_paths(...))Quota exceeded/OperationLimitExceededAOAI TPM cap hit Hand off to quota_throttle_expertImagePullBackOff/pull access deniedACR pull failed Grant AcrPullon the project's ACR to agent's UAMI403 Forbidden /openai/deployments/...Foundry MI lacks Cognitive Services Useron BYOK AOAIGrant role Request body must be a JSON object with a non-empty input stringazd ai agent invokeenvelope bugghcp-hosted-agents KI-001 (use curlwith{"input":"..."})agent.yaml: services: block missingazd ai agent initdoesn't generate itghcp-hosted-agents KI-002 (add manually)
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.
- 7d ago First seen · 62 lines · 51 tokens per session scan A 2ecce2152269
hosted_agent_deploy_expert is a skill published in the GitHub repository aiappsgbb/awesome-gbb (5 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 746 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
gke-ai-troubleshooting-jobset-interruption
Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…
gke-workload-troubleshooting
Diagnoses GKE workload failures (CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending, etc.) via logs and events. Use when pods fail to start or crash repeatedly. Don't use for GKE cluster infrastructure provisioning, node pool creation, or non-Kubernetes Google Cloud services.
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…
gke-ai-troubleshooting-handle-disruption-gpu-tpu
Diagnoses, predicts, and mitigates node disruptions during Compute Engine host maintenance and hardware or software maintenance events for GPU and TPU workloads on GKE. Use when diagnosing node disruptions, predicting host maintenance events on GPU/TPU nodepools, inspecting node interruption PromQL metrics, auditing…
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
troubleshoot-sandbox
Troubleshoot OpenSandbox issues by running diagnostics (logs, inspect, events, summary) via CLI or HTTP API to diagnose sandbox failures like OOM, crash, image pull errors, network problems, etc.