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 vibeeval/vibecosystem --skill azure-patternsgit clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/azure-patterns)<a href="https://agentmods.dev/skills/vibeeval/vibecosystem/azure-patterns"><img src="https://agentmods.dev/badge/skills/vibeeval/vibecosystem/azure-patterns.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.00019 | $0.01750 |
| Opus 5 | $0.00010 | $0.00875 |
| Sonnet 5 | $0.00004 | $0.00350 |
| Haiku 4.5 | $0.00002 | $0.00175 |
Grade A, and why
azure-patterns 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 3d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Patterns
Azure Functions
HTTP Trigger (Node.js v4)
import { app, HttpRequest, HttpResponseInit, InvocationContext } from '@azure/functions';
app.http('getOrder', {
methods: ['GET'],
authLevel: 'function',
route: 'orders/{orderId}',
handler: async (request: HttpRequest, context: InvocationContext): Promise<HttpResponseInit> => {
const orderId = request.params.orderId;
context.log(`Processing order: ${orderId}`);
try {
const order = await orderService.getById(orderId);
if (!order) {
return { status: 404, jsonBody: { error: 'Order not found' } };
}
return { status: 200, jsonBody: order };
} catch (error) {
context.error('Failed to get order', error);
return { status: 500, jsonBody: { error: 'Internal server error' } };
}
},
});
// Service Bus trigger with retry
app.serviceBusTopic('processOrderEvent', {
topicName: 'order-events',
subscriptionName: 'order-processor',
connection: 'ServiceBusConnection',
handler: async (message: unknown, context: InvocationContext) => {
const event = message as OrderEvent;
context.log(`Processing event: ${event.type} for order ${event.orderId}`);
await processEvent(event);
},
});
Durable Functions (Orchestrator)
import * as df from 'durable-functions';
df.app.orchestration('orderWorkflow', function* (context) {
const orderId = context.df.getInput() as string;
// Step 1: Validate order
const order = yield context.df.callActivity('validateOrder', orderId);
// Step 2: Reserve inventory (with retry)
const retryOptions = new df.RetryOptions(5000, 3); // 5s interval, 3 attempts
yield context.df.callActivityWithRetry('reserveInventory', retryOptions, order);
// Step 3: Charge payment
yield context.df.callActivity('chargePayment', order);
// Step 4: Wait for shipping confirmation (with timeout)
const deadline = new Date(context.df.currentUtcDateTime.getTime() + 24 * 60 * 60 * 1000);
const shippingEvent = context.df.waitForExternalEvent('shippingConfirmed');
const timeout = context.df.createTimer(deadline);
const winner = yield context.df.Task.any([shippingEvent, timeout]);
if (winner === timeout) {
yield context.df.callActivity('escalateShipping', orderId);
}
return { orderId, status: 'completed' };
});
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.
- 3d ago First seen · 227 lines · 19 tokens per session scan A 93b5bbf99a89
azure-patterns is a skill published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 29d ago), licensed MIT. It adds 19 tokens to every session and 1,750 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.
hono-api-scaffolder
Scaffold Hono API routes for Cloudflare Workers. Produces route files, middleware, typed bindings, Zod validation, error handling, and APIENDPOINTS.md documentation. Use after a project is set up with cloudflare-worker-builder or vite-flare-starter, when you need to add API routes, create endpoints, or generate API…
cloudflare-worker-builder
Scaffold and deploy Cloudflare Workers with Hono routing, Vite plugin, and Static Assets. Describe project, scaffold structure, configure bindings, deploy. Use whenever the user wants to create a Worker project, set up Hono on Cloudflare, configure D1 / R2 / KV / Queues bindings, or troubleshoot Worker export syntax…
edge-computing
Edge computing with Cloudflare Workers, Deno Deploy, Bun, Vercel Edge Functions, AWS Lambda@Edge, and edge databases (Turso, D1, DynamoDB Global Tables). Use when building low-latency edge applications, edge-side rendering, or globally distributed compute.
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
analyzing-cloud-storage-access-patterns
Detect abnormal access patterns in AWS S3, GCS, and Azure Blob Storage by analyzing CloudTrail Data Events, GCS audit logs, and Azure Storage Analytics. Identifies after-hours bulk downloads, access from new IP addresses, unusual API calls (GetObject spikes), and potential data exfiltration using statistical baselines…