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/ado-master)<a href="https://agentmods.dev/plugins/josiahsiegel/claude-plugin-marketplace/ado-master"><img src="https://agentmods.dev/badge/plugins/josiahsiegel/claude-plugin-marketplace/ado-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/ado-master"><img src="https://agentmods.dev/badge/plugins/josiahsiegel/claude-plugin-marketplace/ado-master.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ado-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 9d 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": "ado-master",
"version": "1.5.9",
"description": "Complete Azure DevOps and Azure Pipelines expertise with Sprint 254-262 features (2025). PROACTIVELY activate for: (1) any Azure DevOps/Pipelines task, (2) YAML pipeline authoring, (3) workload identity federation (OIDC), (4) performance analytics, (5) debugging, (6) CI/CD optimization, (7) security and compliance, (8) Azure DevOps CLI, (9) template management, (10) Microsoft Security DevOps. Provides: workload-identity setup, multi-stage patterns, caching/parallelization, Key Vault integration, code scanning.",
"author": {
"name": "Josiah Siegel",
"email": "[email protected]"
},
"keywords": [
"ado",
"azdo",
"azurepipelines",
"azuredevops",
"yaml",
"pipeline",
"cicd",
"microsoft",
"azure",
"devops",
"security",
"templates",
"defender",
"oidc",
"workload-identity",
"analytics",
"performance",
"windows",
"git-bash",
"mingw",
"cross-platform"
],
"license": "MIT"
}
What it installs
The manifest is a name and a version. 4 skills, 1 agent travel with it, and installing the plugin installs all of them — 885 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.
- 9d ago First seen · 34 lines scan A ad96c678df78
ado-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
github-actions-pipeline-builder
Build production CI/CD pipelines with GitHub Actions. Implements matrix builds, caching, deployments, testing, security scanning. Use for automated testing, deployments, release workflows. Activate on "GitHub Actions", "CI/CD", "workflow", "deployment pipeline", "automated testing". NOT for Jenkins/CircleCI, manual…
github-driven-dev
Comprehensive GitHub workflow orchestration with skills for issues, branches, PRs, and CI management.
nyann
Project governance for Claude Code. Bootstrap and maintain git workflow, hooks, commits, releases, CI, docs, and repo health.
aio-devops
GitHub, GitLab, and git worktree workflows in one toolkit — manage repos, PRs, MRs, pipelines, and parallel branches without juggling CLIs.
charon
Ferries a GitHub PR to merge without waiting forever: an honest snapshot-not-block loop that fixes CI, repairs conflicts, version-checks reviewer suggestions, and never says 'just wait'.
pr-trains
Batch operators for GitHub queues: review-train reviews every open PR, fix-train applies requested changes, fix-ci-train turns red CI green, merge-train fixes and merges in dependency order, issue-train triages and builds one PR per actionable issue — all with parallel sub-agents and one grouped confirmation.