Borrowing it
Nothing to install: this file belongs to Traves-Theberge/Orchestra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Traves-Theberge/Orchestra/main/.codex/skills/maestro-azure-devops/SKILL.mdgit clone --depth 1 https://github.com/Traves-Theberge/OrchestraWrote 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/traves-theberge/orchestra/maestro-azure-devops)<a href="https://agentmods.dev/skills/traves-theberge/orchestra/maestro-azure-devops"><img src="https://agentmods.dev/badge/skills/traves-theberge/orchestra/maestro-azure-devops/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/traves-theberge/orchestra/maestro-azure-devops"><img src="https://agentmods.dev/badge/skills/traves-theberge/orchestra/maestro-azure-devops.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.00034 | $0.00402 |
| Opus 5.5 | $0.00014 | $0.00161 |
| Sonnet 5.5 | $0.00007 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
maestro-azure-devops 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 19d 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
Azure DevOps for Maestro
Read maestro-integrations. Keep Azure organization, project, work item numeric ID, repository ID, and PR ID distinct from Orchestra project/task/workspace IDs. Work item URLs and Repos PR URLs identify different resources.
Orchestra currently has no Azure DevOps tracker adapter in its adapter factory. This skill does not add an account connection or enable issue/task commands. Do not silently route Azure work to GitHub/SQLite, select a different tracker, or report Azure Boards tasks as synchronized. Record the missing capability explicitly in the user's journey.
If an Azure tool or CLI is actually available and the user has authorized its use, validate its organization/project scope and read access before reporting access. Authentication setup belongs in the account/connection flow, never in skill text. Inspect tool help and use the installed version; this skill does not advertise Azure CLI commands that Orchestra has not provided.
The implementation journey is: configure a verified Azure connection, discover exact project/work item identity and process-specific states, provide source-scoped observation/create/assignment with durable receipts, preserve work item revision checks, bind a local execution/workspace separately, attach the exact Repos/GitHub PR URL, then verify review/head/checks before task-state reconciliation. These adapter and reconciliation steps remain unavailable until implemented and behaviorally verified.
For an existing local Orchestra task with Azure PR linkage, preserve the stored PR URL and identify the repository provider without claiming the task originated in Boards. No PR link means no observed linkage.
Primary reference: Azure DevOps Work Items API. Provider API documentation is a design input, not proof of a working Orchestra integration.
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.
- 19d ago First seen · 19 lines · 34 tokens per session scan A 2d1f78d50cf8
maestro-azure-devops is a skill published in the GitHub repository Traves-Theberge/Orchestra (26 stars, last pushed 10d ago), licensed Apache-2.0. It adds 34 tokens to every session and 402 once invoked, about $0.0001 per session on Opus 5.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-10-06.
Other skills, from other repositories
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.
agtx-oneshot
One-shot a whole project on an agtx board: decompose the goal, run every task unattended, unblock the workers, and merge each one. Use when the user wants a long autonomous run rather than a single session.
agtx-sweep
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
start-task
Create a feature branch for a backlog task, switch to it, and start implementation. Use when the user says "start task-123", "work on task-123", "implement task-123", or invokes /start-task with a task ID.
cmux-testing
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.