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 RobinNorberg/oh-my-copilot --skill omc-ado-setupgit clone --depth 1 https://github.com/RobinNorberg/oh-my-copilotWrote 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/robinnorberg/oh-my-copilot/omc-ado-setup)<a href="https://agentmods.dev/skills/robinnorberg/oh-my-copilot/omc-ado-setup"><img src="https://agentmods.dev/badge/skills/robinnorberg/oh-my-copilot/omc-ado-setup/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/robinnorberg/oh-my-copilot/omc-ado-setup"><img src="https://agentmods.dev/badge/skills/robinnorberg/oh-my-copilot/omc-ado-setup.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.00105 | $0.01979 |
| Opus 5 | $0.00053 | $0.00989 |
| Sonnet 5 | $0.00021 | $0.00396 |
| Haiku 4.5 | $0.00011 | $0.00198 |
Grade A, and why
omc-ado-setup 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 5d 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OMC ADO Setup
Configure Azure DevOps integration for the current project. Detects the ADO org and project from the git remote URL, verifies authentication, and writes .omg/config.json with all required settings.
When this skill is invoked, immediately execute the workflow below. Do not only restate or summarize these instructions back to the user.
Trigger Patterns
- "setup ado"
- "configure azure devops"
- "ado setup"
- "connect to azure devops"
- "omc-ado-setup"
Prerequisites
Before running the main workflow, verify all prerequisites are present. If any fail, report the issue and stop with actionable remediation steps.
Check 1: az CLI installed
az --version 2>&1 | head -1
If this fails: tell the user to install the Azure CLI from https://aka.ms/installazurecli.
Check 2: azure-devops extension installed
az extension show --name azure-devops --query name -o tsv 2>&1
If output is not azure-devops: run az extension add --name azure-devops to install it.
Check 3: az authentication status
az account show --query "{name:name, id:id, tenantId:tenantId}" -o json 2>&1
If this fails or returns an error: tell the user to run az login and retry.
Check 4: az devops configured defaults
az devops configure --list 2>&1
Show the output to the user so they can see existing defaults (org, project).
Step 1: Detect ADO Remote
Inspect the git remote URL to determine if the repo is hosted on Azure DevOps.
git remote -v 2>&1
Azure DevOps remote URLs follow these patterns:
https://dev.azure.com/{org}/{project}/_git/{repo}https://{org}.visualstudio.com/{project}/_git/{repo}[email protected]:v3/{org}/{project}/{repo}
Parse the remote URL to extract:
org— the ADO organization nameproject— the ADO project namerepo— the repository name
If no ADO remote is detected, inform the user and ask whether they want to configure manually (prompt for org, project, repo values).
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.
- 5d ago First seen · 248 lines · 105 tokens per session scan A 595e3513e679
omc-ado-setup is a skill published in the GitHub repository RobinNorberg/oh-my-copilot (5 stars, last pushed 3d ago), licensed MIT. It adds 105 tokens to every session and 1,979 once invoked, about $0.0005 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-09-04.
Other skills, from other repositories
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.
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.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
machinist
Use Machinist to create, assign, monitor, and resume software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, lifecycle labels, direct runs, or managed queue.
linear-cli
Use when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write boundaries.
steward-prep-delivery
Steward-assisted prep for filing issues and PRs — environment capture, template selection, duplicate detection, delivery-policy compliance check.