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 jamesyang124/agent-skills --skill ado-open-prgit clone --depth 1 https://github.com/jamesyang124/agent-skillsWrote 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/jamesyang124/agent-skills/ado-open-pr)<a href="https://agentmods.dev/skills/jamesyang124/agent-skills/ado-open-pr"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/ado-open-pr/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/jamesyang124/agent-skills/ado-open-pr"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/ado-open-pr.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.00124 | $0.04869 |
| Opus 5 | $0.00062 | $0.02434 |
| Sonnet 5 | $0.00025 | $0.00974 |
| Haiku 4.5 | $0.00012 | $0.00487 |
Grade A, and why
ado-open-pr 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Azure DevOps Pull Request
⚙️ Dependencies
- Azure DevOps MCP — provides the
repo_*andcore_*tools. Install once with theinstall-azure-devops-mcpskill (writes.mcp.json+~/.env.mcp-azure-devops), then restart your agent. Repository: https://github.com/microsoft/azure-devops-mcp - generate-pr-notes skill — its note-generation contract is reused for the PR description (see Step 4).
Install it globally (
~/.claude/skills/generate-pr-notes/) or import it with.agent-settings/skills/import-skills.sh <agent> generate-pr-notes. - Optional: Azure CLI (
az, logged in) — used only to identify the current user so they are not added as their own reviewer. Falls back togit config user.emailwhenazis unavailable.
This skill lives at .agent-settings/skills/tools/ado-open-pr/ and is auto-discovered by import-skills.sh — no manual copy or registry edit is needed.
Arguments
All optional, any order. Disambiguate each bare (unflagged) token as follows:
| Token shape | Interpreted as |
|---|---|
matches [A-Z]+-\d+ |
Jira ticket |
contains @ |
reviewer email / unique name |
matches a team key under teams in the reviewer config |
reviewer team |
literally draft |
open the PR as a draft |
| anything else | target branch |
Flags: --title <text> (explicit PR title), --ado-project <name>, --ado-repo <name>, --no-sync-spec (skip the Step 1.5 spec-alignment scan, which otherwise runs by default). Default target branch is develop.
Step 1 — Preflight
- Confirm this is a git repo. Read the current branch:
git branch --show-current. - Abort if the branch is empty,
main, ordevelop— a PR must come from a feature branch. Tell the user which branch they are on. - Check the working tree:
git status --porcelain=v1 -b. If there are uncommitted changes, warn: "The PR will only include committed work — uncommitted changes are not part of it." Continue unless the user redirects. - Resolve the target branch from the args; default to
develop. - Resolve the Jira ticket in this order — accept the first
[A-Z]+-\d+match found:- explicit ticket arg
- current branch name
- latest commit subject (
git log --format=%s -1)
- Load the reviewer config now (the merged sources in Step 6) so a bare token can be recognized as a team key during argument parsing. A missing or malformed config is fine here — it just means no team keys are known yet.
- Capture the title candidate now —
git log --format=%s -1— and hold it for Step 4. Do this before Step 1.5 can add adocs(spec): sync to codecommit on top ofHEAD; otherwise that commit would become the PR title.
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 · 217 lines · 124 tokens per session scan A fb80d9474ff6
ado-open-pr is a skill published in the GitHub repository jamesyang124/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 124 tokens to every session and 4,869 once invoked, about $0.0006 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.