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 foundry-caphost-lifecyclegit 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/foundry-caphost-lifecycle)<a href="https://agentmods.dev/skills/aiappsgbb/awesome-gbb/foundry-caphost-lifecycle"><img src="https://agentmods.dev/badge/skills/aiappsgbb/awesome-gbb/foundry-caphost-lifecycle.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Memory Poisoning · line 286 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- medium Agent Snooping · line 35 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00229 | $0.06477 |
| Opus 5 | $0.00114 | $0.03238 |
| Sonnet 5 | $0.00046 | $0.01295 |
| Haiku 4.5 | $0.00023 | $0.00648 |
Grade A, and why
foundry-caphost-lifecycle 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 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.
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 — 491 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Foundry Capability Host Lifecycle — Day-2 Operations
1. Goal
This skill teaches Day-2 operations for Microsoft Foundry capability hosts: how to
inspect, idempotently re-create, delete, soft-delete the parent account,
purge, and redeploy without tripping the Subnet already in use failure that
blocks every team that has ever torn down a VNet-injected Foundry account.
This is explicitly not greenfield create — for first-time BYO-VNet deploys see
foundry-vnet-deploy, and for the azd template
flow see foundry-hosted-agents or
threadlight-deploy.
This skill is the field-experience overlay on top of the MS Learn capability-hosts
page (learn.microsoft.com/azure/foundry/agents/concepts/capability-hosts)
that ships with the operational knowledge MS Learn does not document.
2. When to use
Trigger this skill whenever any of these are true:
- You teardown'd a Foundry VNet-injected account and now
az deployment group createfails withSubnet already in use(orSubnetIsFullreferencing aserviceAssociationLink) when you try to redeploy into the same agent subnet. - A caphost create is stuck in
Creatingfor more than 10 minutes (the upstream operation has a documented ~5-15 min p99; longer means hung — go to § 9). - You need to change the connections referenced by a project capability host (e.g., swap a Cosmos connection). MS Learn is explicit: updates are not supported; delete + recreate is the only path.
- You need to fully reclaim the soft-deleted account name within the 48h window (so a new account can be created with the same custom domain).
- You want a clean teardown that releases the
serviceAssociationLinkon the agent subnet AND removes the hidden ACA Managed Environment that the capability host provisioned under the covers. - You have a soft-deleted account that needs to be recovered (not purged) before the 48h window expires.
What ships with it
2 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.
- 7d ago First seen · 491 lines · 229 tokens per session scan A 8f9b126c2a4a
foundry-caphost-lifecycle is a skill published in the GitHub repository aiappsgbb/awesome-gbb (5 stars, last pushed yesterday), licensed MIT. It adds 229 tokens to every session and 6,477 once invoked, about $0.0011 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…