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/lttr/claude-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/lttr/claude-marketplace/dev-azdo)<a href="https://agentmods.dev/plugins/lttr/claude-marketplace/dev-azdo"><img src="https://agentmods.dev/badge/plugins/lttr/claude-marketplace/dev-azdo/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/lttr/claude-marketplace/dev-azdo"><img src="https://agentmods.dev/badge/plugins/lttr/claude-marketplace/dev-azdo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dev-azdo 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 18d 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": "dev-azdo",
"version": "4.0.0",
"description": "Azure DevOps workflow automation as NL-driven skills: ticket (show, create, comment, state), pr (incl. comment threads), feature-branch. Work items and comments are created via az rest so descriptions render as Markdown.",
"author": {
"name": "Lukas Trumm",
"email": "[email protected]"
},
"keywords": [
"azure-devops",
"azdo",
"git",
"workflow",
"pull-request",
"work-item"
]
}
What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 256 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.
- 18d ago Changed 7b1a8779c60d
- 27d ago Changed · -1 lines 1cac307adaab
- 28d ago Changed · -1 lines eb4815381bc4
- 1mo ago First seen · 20 lines scan A c27e02e3b58d
dev-azdo is a plugin published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed 14d 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-31.
Other plugins, from other repositories
ticket-flow
Beads-backed ticket workflow for Claude Code: spec → pickup → implement → finish behind verdict and merge gates, orchestrated by /flow (--local with resume, --parallel, --serial/--loop unattended queue runner), each ticket in its own git worktree. Five visible commands; the phase skills are model-invoked.
csw
Ship a tracker ticket: dispatch it into a worktree, drive it to a pull request, merge it after review, and clean up after itself.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.
ooda-loop marketplace
Plugin marketplace listing 1 plugin: ooda-loop.
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.
vibe-flow
Orchestration skills for Vibe Kanban: plan → ship → link → review → merge with wave-based dispatch, executor routing (T0-T4), and autonomous fix loops.