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 apex-azure-storagegit 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/apex-azure-storage)<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/apex-azure-storage"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-azure-storage/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/apex-azure-storage"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/apex-azure-storage.svg" alt="Reviewed on agentmods" width="80" 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.00099 | $0.01596 |
| Opus 5.5 | $0.00040 | $0.00638 |
| Sonnet 5.5 | $0.00020 | $0.00319 |
| Haiku 4.5 | $0.00010 | $0.00160 |
Grade A, and why
apex-azure-storage 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 22d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Storage Services
Prerequisites
Confirm account, service, authorized operation and data-plane access. Use installed CLI/SDK capabilities; follow the language leaf's version requirements. Obtain separate authorization before uploads, overwrites, lifecycle changes or downloads that replace local files.
Services
| Service | Use When | CLI |
|---|---|---|
| Blob Storage | Objects, files, backups, static content | az storage blob |
| File Shares | SMB file shares, lift-and-shift | az storage file |
| Queue Storage | Async messaging, task queues | az storage queue |
| Table Storage | NoSQL key-value (consider Cosmos DB) | az storage table |
| Data Lake | Big data analytics, hierarchical namespace | az storage fs |
CLI commands
# List storage accounts
az storage account list --output table
# List containers
az storage container list --account-name ACCOUNT --auth-mode login --output table
# List blobs
az storage blob list --account-name ACCOUNT --container-name CONTAINER --auth-mode login --output table
# Download blob
az storage blob download --account-name ACCOUNT --container-name CONTAINER --name BLOB --file LOCAL_PATH --auth-mode login
# Upload blob
az storage blob upload --account-name ACCOUNT --container-name CONTAINER --name BLOB --file LOCAL_PATH --auth-mode login
These data-plane commands use the signed-in Entra identity. It needs scoped Storage Blob Data Reader for reads or Storage Blob Data Contributor for writes; management-plane Reader alone is insufficient.
For deeper service docs and patterns, call mcp_azure-mcp_documentation
with command: "microsoft_docs_search" and the relevant Azure Storage
topic, or follow the links in Service Details.
Storage Account Tiers
| Tier | Use Case | Performance |
|---|---|---|
| Standard | General purpose, backup | Milliseconds |
| Premium | Databases, high IOPS | Sub-millisecond |
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/sdk-usage.md 5.2 KB
- references/sdk/azure-data-tables-java.md 1.3 KB
- references/sdk/azure-data-tables-py.md 1.1 KB
- references/sdk/azure-storage-blob-java.md 1.4 KB
- references/sdk/azure-storage-blob-py.md 1.0 KB
- references/sdk/azure-storage-blob-rust.md 2.2 KB
- references/sdk/azure-storage-blob-ts.md 1.2 KB
- references/sdk/azure-storage-file-datalake-py.md 1.4 KB
- references/sdk/azure-storage-file-share-py.md 1.0 KB
- references/sdk/azure-storage-file-share-ts.md 1.3 KB
- references/sdk/azure-storage-queue-py.md 1.1 KB
- references/sdk/azure-storage-queue-ts.md 1.3 KB
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.
- 22d ago Changed · -11 tokens per session 25f2f47b100a
- 23d ago First seen · 131 lines · 110 tokens per session scan A 406d1896edf6
apex-azure-storage is a skill published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 1,596 once invoked, about $0.0004 per session on Opus 5.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-23.
Other skills, from other repositories
chaos-experiment
Design and document chaos engineering experiments. Guide steady state baseline, hypothesis formation, failure injection plans, and results analysis. Use when you say "design a chaos experiment", "plan a game day", "failure injection", "test resilience", or "chaos engineering". Do NOT use for security threat analysis…
infrastructure-as-code
Domain: DevOps & Cloud Engineering.
cloud-solution-architect
Design well-architected Azure cloud systems — 10 design principles, 6 architecture styles, 44 design patterns, technology choices, WAF pillars.
bicep-avm-mastery
Azure Verified Modules (AVM), Bicep best practices, and MCP-powered infrastructure as code for Azure.
foundry-agent-platform
Microsoft Foundry agent deployment, orchestration, and cloud-native AI service patterns.
sse-streaming
POST-based Server-Sent Events streaming for Azure Functions — HTTP streaming, chunked response parsing, reconnection.