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 ahmadharis/agentskills --skill azure-workgit clone --depth 1 https://github.com/ahmadharis/agentskillsWrote 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/ahmadharis/agentskills/azure-work)<a href="https://agentmods.dev/skills/ahmadharis/agentskills/azure-work"><img src="https://agentmods.dev/badge/skills/ahmadharis/agentskills/azure-work/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/ahmadharis/agentskills/azure-work"><img src="https://agentmods.dev/badge/skills/ahmadharis/agentskills/azure-work.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.00128 | $0.05768 |
| Opus 5 | $0.00064 | $0.02884 |
| Sonnet 5 | $0.00026 | $0.01154 |
| Haiku 4.5 | $0.00013 | $0.00577 |
Grade D, and why
azure-work scanned grade D with 3 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 8d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Linux**: `curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash` Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- **Linux**: `curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Linux**: `curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash` How it starts
The opening of the file, as written. The whole thing — 598 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure DevOps Work Item Workflow
Browse, pick up, implement, create, and update Azure DevOps work items.
Invocation
| Mode | Command | Behavior |
|---|---|---|
| Browse | /azure-work |
List open work items, user picks one |
| Direct | /azure-work <number> |
Go straight to that work item |
| Create | /azure-work create |
Create a new work item |
| Update | /azure-work update <number> |
Update an existing work item's fields |
Prerequisites
Verify az CLI is available before proceeding. Run:
az --version
If the command fails, inform the user how to install it:
- macOS:
brew install azure-cli - Windows:
winget install --exact --id Microsoft.AzureCLI - Linux:
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash
Windows shell requirement: All commands in this skill use bash syntax (sed, mktemp, curl, etc.). On Windows, run in Git Bash or WSL — PowerShell and cmd are not supported.
Then ensure the Azure DevOps extension is installed:
az extension add --name azure-devops
Setup (First Run Only)
On first invocation, the skill needs Azure CLI authentication and a backlog URL.
1. Verify Azure CLI Authentication
az account show
If not authenticated, run az login --allow-no-subscriptions which opens the browser for Azure AD OAuth. No PAT tokens or stored credentials are needed.
2. Check for Configuration
Check if the ADO_BACKLOG_URL environment variable is set. If it IS set, ADO_ORG and ADO_PROJECT should also be available (and ADO_TEAM if the URL contained a team) — skip to the Workflow section.
If ADO_BACKLOG_URL is NOT set, prompt the user:
"What's your Azure DevOps backlog URL?" (e.g.,
https://dev.azure.com/org/project/_backlogs/backlog/team/Backlog%20items)
Note: The URL may or may not include a team segment. Both formats are valid:
- With team:
https://dev.azure.com/org/project/_backlogs/backlog/team/Backlog%20items - Without team:
https://dev.azure.com/org/project/_backlogs/backlog/Backlog%20items - Board URL also accepted:
https://dev.azure.com/org/project/_boards/board/t/team/Backlog%20items
What ships with it
1 file 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.
- 8d ago First seen · 598 lines · 128 tokens per session scan D 7b4ec8b427b6
azure-work is a skill published in the GitHub repository ahmadharis/agentskills (2 stars, last pushed 5mo ago), licensed MIT. It adds 128 tokens to every session and 5,768 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.