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-routinesgit 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-routines)<a href="https://agentmods.dev/skills/aiappsgbb/awesome-gbb/foundry-routines"><img src="https://agentmods.dev/badge/skills/aiappsgbb/awesome-gbb/foundry-routines/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/aiappsgbb/awesome-gbb/foundry-routines"><img src="https://agentmods.dev/badge/skills/aiappsgbb/awesome-gbb/foundry-routines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00218 | $0.04099 |
| Opus 5 | $0.00109 | $0.02049 |
| Sonnet 5 | $0.00044 | $0.00820 |
| Haiku 4.5 | $0.00022 | $0.00410 |
Grade A, and why
foundry-routines 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 10d 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 — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microsoft Foundry Routines — Reference Guide
A routine is a named automation rule that fires an existing Foundry agent on a schedule (cron) or at a specific moment (timer). The Foundry service queues the invocation, runs the agent, and stores a run record you can inspect later. Routines remove the need to host your own scheduler (Functions, Logic Apps, cron jobs) around an agent that already lives in Foundry.
Status: preview (regional). Send the
Foundry-Features: Routines=V1Previewheader on every REST call (the SDK adds it automatically). Available in a subset of regions — see § 2.
1 · What & when
A routine has exactly one trigger and one action.
| Concept | Values |
|---|---|
| Trigger | schedule (cron, ≥ 5 min interval) or timer (one-shot at a future timestamp / duration) |
| Action | invoke_agent_responses_api (call agent via Responses API) or invoke_agent_invocations_api (call via Invocations API) |
| Lifecycle | Created enabled or disabled, then enable / disable / delete |
| Run history | Every fire is recorded — query via SDK, REST, or portal |
When to reach for routines
| Scenario | Use routines? |
|---|---|
| Run a Foundry agent every weekday at 07:00 UTC | ✅ Yes — schedule trigger |
| Run a Foundry agent once at a fixed future timestamp | ✅ Yes — timer trigger |
| Test an agent on-demand without waiting for its schedule | ✅ Yes — dispatch() manual dispatch |
| Multi-step workflow (call agent A, branch on result, call agent B) | ❌ No — use Foundry workflows |
| Event-driven trigger (HTTP webhook, queue message, file upload) | ❌ No — use Azure Functions / Event Grid / Logic Apps and call the agent from there |
| Sub-minute precision schedule | ❌ No — 5-minute minimum interval |
Routines complement, not replace, foundry-prompt-agents and
foundry-hosted-agents — those skills create the agent; this
skill schedules its invocation.
2 · Prerequisites
- Microsoft Foundry project in one of the routines-preview regions (verified against the routines concept doc — see § 10):
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.
- 10d ago First seen · 417 lines · 218 tokens per session scan A 40bf2200c55f
foundry-routines is a skill published in the GitHub repository aiappsgbb/awesome-gbb (5 stars, last pushed 3d ago), licensed MIT. It adds 218 tokens to every session and 4,099 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…