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 agentmods add skills/techwatching/copilot-goodies/azure-devopsnpx skills add TechWatching/copilot-goodies --skill azure-devopsgit clone --depth 1 https://github.com/TechWatching/copilot-goodiesWhat 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 | $0.00038 | $0.00315 |
| Opus 5 | $0.00019 | $0.00158 |
| Sonnet 5 | $0.00008 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
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 3d 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 Configuration
Organization & Project
- Organization:
<ADO_ORG> - Project Name:
<ADO_PROJECT_NAME> - Project ID:
<ADO_PROJECT_ID> - Organization URL:
https://dev.azure.com/<ADO_ORG> - Project URL:
https://dev.azure.com/<ADO_ORG>/<ADO_PROJECT_URL_SEGMENT>
Work Item Types
- Epic
- Feature
- User Story
- Bug
- Task
Usage Guidelines
- Always pass
project: <ADO_PROJECT_NAME>. - Use the correct repository ID for branch/commit/PR artifact linking.
- Output work-item links as:
https://dev.azure.com/<ADO_ORG>/<ADO_PROJECT_URL_SEGMENT>/_workitems/edit/{workItemId} - Use Markdown format for long text fields.
- Read the current work item before update to avoid overwriting concurrent changes.
- Follow existing tags/naming/field usage conventions from current project data.
Optional per-workspace extensions
Add or remove sections depending on your environment:
- Iteration/team defaults
- Deployment-specific required fields
- PR/repo mapping conventions
- Pipeline/release linking conventions
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.
- 3d ago First seen · 41 lines · 38 tokens per session scan A c7cc864b19c6
azure-devops is a skill published in the GitHub repository TechWatching/copilot-goodies (8 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 315 once invoked, about $0.0002 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
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
dsh-web-pre-push-checks
Use before pushing, opening or updating a pull request, or claiming dsh-web checks pass. Selects the required repository gates and diff-specific generation, build, and GUI evidence.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
harness-setup
HAR: Project init, tool setup, agent config, memory setup, skill mirror sync. Trigger: setup, init, new project, CI/Codex setup, harness-mem, mirror. Do NOT load for: implementation, review, release, planning.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.