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/charlesjones-dev/claude-code-plugins-dev/ado-initnpx skills add charlesjones-dev/claude-code-plugins-dev --skill ado-initgit clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-devWhat 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.00022 | $0.03917 |
| Opus 5 | $0.00011 | $0.01959 |
| Sonnet 5 | $0.00004 | $0.00783 |
| Haiku 4.5 | $0.00002 | $0.00392 |
Grade A, and why
ado-init 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 2d 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 — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure DevOps Init
Initialize Azure DevOps configuration by creating or updating CLAUDE.md with your organization, project, and team settings, and optionally configuring the Azure DevOps MCP server.
Instructions
CRITICAL: This command MUST NOT accept any arguments. If the user provided any text, organization names, project names, or other arguments after this command (e.g., /ado-init myorg or /ado-init myorg/myproject), you MUST COMPLETELY IGNORE them. Do NOT use any organization names, project names, or other arguments that appear in the user's message. You MUST ONLY gather requirements through the interactive sequential prompts as specified below.
BEFORE DOING ANYTHING ELSE: Begin with Phase 1 by asking for the organization name. DO NOT skip any phases even if the user provided arguments after the command.
Configure CLAUDE.md with Azure DevOps-specific settings that guide Claude Code when working with the Microsoft Azure DevOps MCP server tools. Detailed work item creation guidelines are provided by the ado-work-items skill.
Phase 1: Gather Azure DevOps Configuration
Collect Azure DevOps settings from the user in a sequential flow. Ask for each value and wait for the user's response before proceeding to the next.
Step 1 - Organization:
Simply output the following text as your response message and STOP (DO NOT call any tools, especially not AskUserQuestion):
"What is your Azure DevOps organization name? (This is the organization URL segment, e.g., 'contoso' in dev.azure.com/contoso)"
Wait for the user's next message with their organization name before proceeding.
Step 2 - Project:
After receiving the organization name, simply output the following text as your response message and STOP (DO NOT call any tools):
"What is your Azure DevOps project name?"
Wait for the user's next message with their project name before proceeding.
Step 3 - Team:
After receiving the project name, simply output the following text as your response message and STOP (DO NOT call any tools):
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.
- 2d ago First seen · 418 lines · 22 tokens per session scan A 92e2ff4c3c73
ado-init is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (34 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 3,917 once invoked, about $0.0001 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-30.
Other skills, from other repositories
gwm
Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…