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 akin-ozer/cc-devops-skills --skill azure-pipelines-validatorgit clone --depth 1 https://github.com/akin-ozer/cc-devops-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/akin-ozer/cc-devops-skills/azure-pipelines-validator)<a href="https://agentmods.dev/skills/akin-ozer/cc-devops-skills/azure-pipelines-validator"><img src="https://agentmods.dev/badge/skills/akin-ozer/cc-devops-skills/azure-pipelines-validator/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/akin-ozer/cc-devops-skills/azure-pipelines-validator"><img src="https://agentmods.dev/badge/skills/akin-ozer/cc-devops-skills/azure-pipelines-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 181 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00025 | $0.01459 |
| Opus 5.5 | $0.00010 | $0.00584 |
| Sonnet 5.5 | $0.00005 | $0.00292 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
azure-pipelines-validator scanned grade A with 1 finding 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl-pipe-shell` How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Pipelines Validator
Use this skill to validate Azure DevOps pipeline YAML (azure-pipelines.yml / azure-pipelines.yaml) with local scripts first, then escalate to docs only when local output is not enough.
Trigger Phrases
Use this skill when the user asks things like:
- "Validate my
azure-pipelines.yml." - "Why is this Azure pipeline YAML failing?"
- "Run a security scan on this Azure DevOps pipeline."
- "Check this pipeline for best-practice issues."
- "Review this pipeline in CI before merge."
Do not use this skill for pipeline generation from scratch. Use azure-pipelines-generator for that.
Deterministic Path Setup (No Ambiguity)
Run from any directory using explicit absolute paths:
REPO_ROOT="$(git rev-parse --show-toplevel 2>/dev/null)"
SKILL_DIR="$REPO_ROOT/devops-skills-plugin/skills/azure-pipelines-validator"
PIPELINE_FILE="$REPO_ROOT/azure-pipelines.yml"
If REPO_ROOT is empty, stop and ask for the repository root path. Do not guess paths.
Validate one file:
bash "$SKILL_DIR/scripts/validate_azure_pipelines.sh" "$PIPELINE_FILE"
Auto-detect from current directory (up to depth 3):
bash "$SKILL_DIR/scripts/validate_azure_pipelines.sh"
If auto-detect returns multiple files, rerun with one explicit file path.
Local-First Execution Model
- Preflight
- Confirm
bashandpython3are available. - Confirm target file exists.
- Run local validator
- Default full pass:
bash "$SKILL_DIR/scripts/validate_azure_pipelines.sh" "$PIPELINE_FILE"
- Syntax only:
bash "$SKILL_DIR/scripts/validate_azure_pipelines.sh" "$PIPELINE_FILE" --syntax-only
- Best practices only:
bash "$SKILL_DIR/scripts/validate_azure_pipelines.sh" "$PIPELINE_FILE" --best-practices
- Security only:
bash "$SKILL_DIR/scripts/validate_azure_pipelines.sh" "$PIPELINE_FILE" --security-only
- Strict mode (warnings fail):
bash "$SKILL_DIR/scripts/validate_azure_pipelines.sh" "$PIPELINE_FILE" --strict
What ships with it
21 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .gitignore 11 B
- assets/.yamllint 1.8 KB
- docs/azure-pipelines-reference.md 7.6 KB
- examples/basic-pipeline.yml 2.5 KB
- examples/deployment-pipeline.yml 3.5 KB
- examples/docker-build.yml 1.6 KB
- examples/multi-platform.yml 1.4 KB
- examples/regression-conditional-danger.yml 187 B
- examples/regression-runonce-on-failure.yml 308 B
- examples/template-conditional-stages.yml 529 B
- examples/template-conditional-steps.yml 587 B
- examples/template-example.yml 1.3 KB
- examples/test-with-issues.yml 690 B
- scripts/check_best_practices.py 20 KB runs code
- scripts/check_security.py 22 KB runs code
- scripts/python_wrapper.sh 2.6 KB runs code
- scripts/step_walker.py 5.3 KB runs code
- scripts/test_regressions.py 4.2 KB runs code
- scripts/validate_azure_pipelines.sh 11 KB runs code
- scripts/validate_syntax.py 25 KB runs code
- scripts/yamllint_check.sh 1.6 KB runs code
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.
- 2mo ago First seen · 203 lines · 25 tokens per session scan A 6f2971f08868
azure-pipelines-validator is a skill published in the GitHub repository akin-ozer/cc-devops-skills (332 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 1,459 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
azure-pipelines-validator compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| azure-pipelines-validatorakin-ozer/cc-devops-skills | Skill | 332 | 3mo ago | Apache-2.0 | A | 25 | Claude Code |
| chinese-git-workflowjnMetaCode/superpowers-zh | Skill | 8.5k | 11d ago | MIT | A | 69 | Claude Code |
| atmos-profilescloudposse/atmos | Skill | 1.4k | yesterday | Apache-2.0 | A | 35 | Claude Code |
| webhook-managementhoangsonww/Claude-Code-Agent-Monitor | Skill | 1.1k | yesterday | MIT | A | 56 | Claude Code, Codex |
| monorepo-managementwshobson/agents | Skill | 42k | yesterday | MIT | C | 54 | Claude Code |
| managing-github-actions-secretsPostHog/posthog-foss | Skill | 728 | yesterday | MIT | A | 67 | Claude Code, Codex |
| postman-newman-automationLambdaTest/agent-skills | Skill | 390 | yesterday | MIT | A | 156 | Claude Code, Codex |