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/pantheon-org/tekhne/validatornpx skills add pantheon-org/tekhne --skill validatorgit clone --depth 1 https://github.com/pantheon-org/tekhneWhat 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.00135 | $0.02066 |
| Opus 5 | $0.00068 | $0.01033 |
| Sonnet 5 | $0.00027 | $0.00413 |
| Haiku 4.5 | $0.00014 | $0.00207 |
Grade A, and why
azure-pipelines-validator 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.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Pipelines Validator
Validates, lints, and security-scans Azure DevOps Pipeline configurations (azure-pipelines.yml, azure-pipelines.yaml). Runs four validation layers via a single orchestrator script.
Basic Usage
# Full validation (all layers)
bash .claude/skills/azure-pipelines-validator/scripts/validate_azure_pipelines.sh azure-pipelines.yml
Layers executed in order: 0. YAML lint (yamllint) — formatting, indentation, trailing spaces
- Syntax validation — schema, required fields, stages/jobs/steps hierarchy, task format, dependencies
- Best practices — display names, task version pinning, pool image specificity, caching, timeouts
- Security scan — hardcoded secrets/API keys/AWS/Azure credentials, dangerous script patterns, SSL bypasses, container
:latesttags
Common Options
# Targeted runs
bash scripts/validate_azure_pipelines.sh azure-pipelines.yml --syntax-only
bash scripts/validate_azure_pipelines.sh azure-pipelines.yml --best-practices
bash scripts/validate_azure_pipelines.sh azure-pipelines.yml --security-only
# Skip layers
bash scripts/validate_azure_pipelines.sh azure-pipelines.yml --skip-yaml-lint
bash scripts/validate_azure_pipelines.sh azure-pipelines.yml --no-best-practices
bash scripts/validate_azure_pipelines.sh azure-pipelines.yml --no-security
# Strict mode (fail on warnings)
bash scripts/validate_azure_pipelines.sh azure-pipelines.yml --strict
Individual Scripts
python3 scripts/validate_syntax.py azure-pipelines.yml
python3 scripts/check_best_practices.py azure-pipelines.yml
python3 scripts/check_security.py azure-pipelines.yml
Output and Error Recovery
════════════════════════════════════════════════════════════════════════════════
Azure Pipelines Validator
════════════════════════════════════════════════════════════════════════════════
[1/3] Running syntax validation...
✓ Syntax validation passed
[2/3] Running best practices check...
SUGGESTIONS (2):
INFO: Line 15: Job 'BuildJob' should have displayName [missing-displayname]
💡 Add 'displayName: "Your Job Description"' to job 'BuildJob'
WARNING: Line 25: Task 'Npm@1' could benefit from caching [missing-cache]
💡 Add Cache@2 task to cache dependencies and speed up builds
[3/3] Running security scan...
MEDIUM SEVERITY (1):
MEDIUM: Line 8: Container 'linux' uses ':latest' tag [container-latest-tag]
🔒 Pin container images to specific versions or SHA digests
What ships with it
34 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.
- .audits/2026-03-02/analysis.md 1.1 KB
- .audits/2026-03-02/audit.json 422 B
- .audits/2026-03-02/remediation-plan.md 2.9 KB
- .audits/latest 10 B
- assets/.yamllint 1.8 KB
- assets/examples/basic-pipeline.yml 1.8 KB
- assets/examples/deployment-pipeline.yml 3.5 KB
- assets/examples/docker-build.yml 1.6 KB
- assets/examples/multi-platform.yml 1.4 KB
- assets/examples/template-example.yml 1.3 KB
- assets/examples/test-with-issues.yml 690 B
- evals/instructions.json 994 B
- evals/scenario-01.md 4.3 KB
- evals/scenario-01/capability.txt 73 B
- evals/scenario-01/criteria.json 573 B
- evals/scenario-01/task.md 183 B
- evals/scenario-02.md 3.6 KB
- evals/scenario-02/capability.txt 61 B
- evals/scenario-02/criteria.json 629 B
- evals/scenario-02/task.md 175 B
- evals/scenario-03.md 4.6 KB
- evals/scenario-03/capability.txt 47 B
- evals/scenario-03/criteria.json 637 B
- evals/scenario-03/task.md 173 B
- evals/scenario-04.md 4.4 KB
- evals/scenario-05.md 4.4 KB
- evals/summary.json 555 B
- references/azure-pipelines-reference.md 7.6 KB
- scripts/check_best_practices.py 21 KB runs code
- scripts/check_security.py 24 KB runs code
- scripts/python_wrapper.sh 1.9 KB runs code
- scripts/validate_azure_pipelines.sh 11 KB runs code
- scripts/validate_syntax.py 20 KB runs code
- scripts/yamllint_check.sh 1.7 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.
- 3d ago First seen · 205 lines · 135 tokens per session scan A f9d3c7b7bd34
azure-pipelines-validator is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed 8d ago), licensed MIT. It adds 135 tokens to every session and 2,066 once invoked, about $0.0007 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
comet-github-ci-triage
使用 PR 当前准确 head、失败 job 日志、本地复现边界和可合并状态,诊断 Comet PR 的 GitHub Actions 与覆盖率检查。PR 出现 CI 报错、Codecov 问题、过期检查或无法解释的红色 job 时使用。.
review-tooling
Detect what dev tooling infrastructure a project has and flag gaps across linters, formatters, pre-commit hooks, test runners, and CI/CD pipelines. Returns structured findings without applying changes. Use when the user asks to "review tooling", "check project tooling", "what tooling is missing", "review dev…
aws-cloudformation-task-ecs-deploy-gh
Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready…
devops-pipeline
Configure pre-commit hooks and lean GitHub Actions for shift-left quality assurance. Use when adding or auditing CI/CD to maximize local test coverage and minimize CI cost. Skip for Terraform/K8s, deployment pipelines, or non-GitHub CI providers.
pentest-supply-chain
Software supply chain security — dependency confusion, CI/CD pipeline attacks, lockfile integrity, and build artifact verification.
offensive-supply-chain
Comprehensive offensive methodology for software supply chain attacks covering the full kill chain from reconnaissance through exploitation. Addresses dependency confusion across npm, PyPI, and NuGet ecosystems where internal registry override allows an attacker to inject malicious packages that shadow private…