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 lttr/claude-marketplace --skill az-cligit 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/skills/lttr/claude-marketplace/az-cli)<a href="https://agentmods.dev/skills/lttr/claude-marketplace/az-cli"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/az-cli/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/lttr/claude-marketplace/az-cli"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/az-cli.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.00073 | $0.00904 |
| Opus 5 | $0.00036 | $0.00452 |
| Sonnet 5 | $0.00015 | $0.00181 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
az-cli 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure DevOps CLI
Overview
Manage Azure DevOps resources using the az CLI with the azure-devops extension. Covers repositories, pull requests, pipelines, boards, and work items.
Prerequisites
# Install azure-devops extension (requires az cli 2.30+)
az extension add --name azure-devops
# Authenticate
az login
# Set defaults (recommended)
az devops configure --defaults organization=https://dev.azure.com/YOUR_ORG project=YOUR_PROJECT
Most-Used Commands
My Pull Requests
# List PRs I created
az repos pr list --creator "$(az account show --query user.name -o tsv)"
# List PRs assigned to me for review
az repos pr list --reviewer "$(az account show --query user.name -o tsv)"
# Show PR details
az repos pr show --id <pr-id>
# Checkout PR locally
az repos pr checkout --id <pr-id>
My Work Items
# List work items assigned to me
az boards query --wiql "SELECT [System.Id], [System.Title], [System.State] FROM WorkItems WHERE [System.AssignedTo] = @Me AND [System.State] <> 'Closed' ORDER BY [System.ChangedDate] DESC"
# Show work item details
az boards work-item show --id <work-item-id>
# Create work item
az boards work-item create --title "Task title" --type "Task"
# Update work item state
az boards work-item update --id <id> --state "In Progress"
Pipelines
# List pipelines
az pipelines list
# List recent runs
az pipelines runs list --top 10
# Run a pipeline
az pipelines run --name "pipeline-name"
# Run with parameters
az pipelines run --name "pipeline-name" --parameters "env=prod version=1.0"
# Show run details
az pipelines runs show --id <run-id>
Repositories
# List repositories
az repos list
# Show repo details
az repos show --repository <repo-name>
# Create repository
az repos create --name "new-repo"
Pull Request Workflow
# Create PR
az repos pr create --source-branch feature/my-branch --target-branch main --title "PR Title" --description "Description"
# Add reviewers
az repos pr update --id <pr-id> --reviewers [email protected]
# Set vote (approve: 10, approve with suggestions: 5, wait: -5, reject: -10)
az repos pr set-vote --id <pr-id> --vote 10
# Complete/merge PR
az repos pr update --id <pr-id> --status completed
What ships with it
4 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.
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 · 139 lines · 73 tokens per session scan A 754d1f30d9d8
az-cli is a skill published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 904 once invoked, about $0.0004 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-31.
Other skills, from other repositories
issue-triage
Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).
multi-agent
A process for coordinating multiple coding agents by splitting work among scouts, workers, reviewers, and repair agents. Each agent has a defined role and task.
tencent-meeting-mcp
A Tencent Meeting assistant for scheduling meetings and working with participants, recordings, transcripts, and AI-generated meeting notes.
flow-next-plan
Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
project-execution
Executes implementation plans with progress tracking, checkpoint validation, and quality gates. Use after planning is complete and tasks are ready to implement.