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 jonathan-vella/apex-accelerator --skill azure-messaginggit clone --depth 1 https://github.com/jonathan-vella/apex-acceleratorWrote 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/jonathan-vella/apex-accelerator/azure-messaging)<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/azure-messaging"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/azure-messaging/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/jonathan-vella/apex-accelerator/azure-messaging"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/azure-messaging.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.00135 | $0.00862 |
| Opus 5 | $0.00068 | $0.00431 |
| Sonnet 5 | $0.00027 | $0.00172 |
| Haiku 4.5 | $0.00014 | $0.00086 |
Grade A, and why
azure-messaging 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- azure-messaging — 88% identical, 38 lines differ
- azure-messaging — 88% identical, 38 lines differ
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Messaging SDK Troubleshooting
Quick Reference
| Property | Value |
|---|---|
| Services | Azure Event Hubs, Azure Service Bus |
| MCP Tools | mcp_azure_mcp_eventhubs, mcp_azure_mcp_servicebus |
| Best For | Diagnosing SDK connection, auth, and message processing issues |
When to Use This Skill
- SDK connection failures, auth errors, or AMQP link errors
- Message lock lost, session lock, or send/receive timeouts
- Event processor or message handler stops processing
- SDK configuration questions (retry, prefetch, batch size)
MCP Tools
| Tool | Command | Use |
|---|---|---|
mcp_azure_mcp_eventhubs |
Namespace/hub ops | List namespaces, hubs, consumer groups |
mcp_azure_mcp_servicebus |
Queue/topic ops | List namespaces, queues, topics, subscriptions |
mcp_azure_mcp_monitor |
logs_query |
Query diagnostic logs with KQL |
mcp_azure_mcp_resourcehealth |
get |
Check service health status |
mcp_azure_mcp_documentation |
Doc search | Search Microsoft Learn for troubleshooting docs |
Diagnosis Workflow
- Identify the SDK and version — Ask which language SDK and version the user is on
- Check resource health — Use
mcp_azure_mcp_resourcehealthto verify the namespace is healthy - Review the error message — Match against language-specific troubleshooting guide
- Look up documentation — Use
mcp_azure_mcp_documentationto search Microsoft Learn for the error or topic - Check configuration — Verify connection string, entity name, consumer group
- Recommend fix — Apply remediation, citing documentation found
What ships with it
12 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.
- references/auth-best-practices.md 6.4 KB
- references/sdk/azure-eventhubs-dotnet.md 4.1 KB
- references/sdk/azure-eventhubs-java.md 3.5 KB
- references/sdk/azure-eventhubs-js.md 2.9 KB
- references/sdk/azure-eventhubs-py.md 3.9 KB
- references/sdk/azure-servicebus-dotnet.md 3.9 KB
- references/sdk/azure-servicebus-java.md 2.6 KB
- references/sdk/azure-servicebus-js.md 3.5 KB
- references/sdk/azure-servicebus-py.md 3.5 KB
- references/service-troubleshooting.md 5.0 KB
- SKILL.digest.md 1.9 KB
- SKILL.minimal.md 514 B
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 · 67 lines · 135 tokens per session scan A 2d428a0b98f7
azure-messaging is a skill published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed 2d ago), licensed MIT. It adds 135 tokens to every session and 862 once invoked, about $0.0007 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-30.
Other skills, from other repositories
error-recovery-patterns
What to do when things break.
error-handling-patterns
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
azure-messaging
Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue…
bfl-api
BFL FLUX API integration guide covering endpoints, async polling patterns, rate limiting, error handling, webhooks, and regional endpoints with Python and TypeScript code examples.
data-fetching
Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, axios, React Query, SWR, error handling, caching strategies, offline support.
github-fix-issue
Analyze and fix GitHub issues in the current repository, including issue research, scoped implementation, and testing. Use when the user asks to fix, investigate, or work on a GitHub issue by number or URL. Create branches, commits, pushes, or pull requests only when the user explicitly requests those delivery actions.