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.
git clone --depth 1 https://github.com/JosiahSiegel/claude-plugin-marketplaceWrote 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/plugins/josiahsiegel/claude-plugin-marketplace/azure-to-docker-master)<a href="https://agentmods.dev/plugins/josiahsiegel/claude-plugin-marketplace/azure-to-docker-master"><img src="https://agentmods.dev/badge/plugins/josiahsiegel/claude-plugin-marketplace/azure-to-docker-master/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/plugins/josiahsiegel/claude-plugin-marketplace/azure-to-docker-master"><img src="https://agentmods.dev/badge/plugins/josiahsiegel/claude-plugin-marketplace/azure-to-docker-master.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
azure-to-docker-master 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 11d 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.
What it actually says
{
"name": "azure-to-docker-master",
"version": "1.1.9",
"description": "Complete Azure-to-Docker migration for local development with 2025 emulators. PROACTIVELY activate for: (1) any Azure-to-Docker migration, (2) Azure infra extraction and Compose generation, (3) emulator setup (Azurite, SQL Server 2025, Cosmos DB vnext, Service Bus), (4) Compose Watch hot reload, (5) database export from Azure SQL/Postgres/MySQL, (6) Dockerfile generation from App Service, (7) multi-container orchestration, (8) health checks and runtime secrets, (9) service mapping (App Service/SQL/Storage/Redis/Cosmos), (10) dev-to-prod parity.",
"author": {
"name": "Josiah Siegel",
"email": "[email protected]"
},
"keywords": [
"azure",
"docker",
"migration",
"compose",
"emulator",
"azurite",
"local-dev",
"infrastructure",
"extraction",
"containerize",
"sql-server",
"cosmos",
"storage",
"watch-mode",
"hot-reload",
"service-bus"
],
"license": "MIT"
}
What it installs
The manifest is a name and a version. 3 skills, 2 commands, 1 agent travel with it, and installing the plugin installs all of them — 700 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 11d ago First seen · 29 lines scan A 0f26187c6489
azure-to-docker-master is a plugin published in the GitHub repository JosiahSiegel/claude-plugin-marketplace (54 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
agent-sandboxing
Agent sandboxing for AI coding agents: microVM and kernel-isolated execution environments. Index skill (sandbox) routes to substrate-specific paths. Currently covers the kubernetes-sigs/agent-sandbox path on kind, GKE, and kina (Kubernetes-in-Apple-Containers), with Kata, gVisor, and Apple Container microVM substrates.
monk
Deploy and operate full applications with Monk DevOps Agent — cloud infra, SaaS integrations, and containerized workloads — from one chat. Bundles the monk skill and blocks accidental monk CLI shell-outs that would desync cluster state.
ensemble-infrastructure
Infrastructure management for AWS, Kubernetes, Docker, Helm, Fly.io.
daytona
Creates and manages isolated cloud sandboxes (secure code execution environments with dedicated runtimes) on the Daytona platform.
open-forge
Self-host open-source apps on your own cloud, your own VPS, your own Kubernetes cluster, a PaaS, or your own laptop. Chat-friendly interface to existing tools (aws, az, hcloud, doctl, gcloud, flyctl, kubectl, helm, podman, docker, lume, tailscale, terraform, cdk, ssh, gh) — Claude runs every command; you only answer…
agentic-workflows
Intelligent multi-agent swarms for automation - Ansible collections, Kubernetes operators, Terraform modules.