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 pantheon-org/tekhne --skill validatorgit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/validator)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/validator"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/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/pantheon-org/tekhne/validator"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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 Rogue Agent · line 156 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00135 | $0.02840 |
| Opus 5.5 | $0.00054 | $0.01136 |
| Sonnet 5.5 | $0.00027 | $0.00568 |
| Haiku 4.5 | $0.00014 | $0.00284 |
Grade B, and why
azure-pipelines-validator scanned grade B with 2 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 12d 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- Auditing a pipeline for hardcoded secrets, `:latest` container tags or `curl | bash` patterns. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Auditing a pipeline for hardcoded secrets, `:latest` container tags or `curl | bash` patterns. How it starts
The opening of the file, as written. The whole thing — 262 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.
Philosophy
- Static analysis is cheap and runs before the pipeline does, so catch problems at review time, not at queue time.
- Fix findings in layer order (lint, syntax, best practices, security): a syntax error can hide later findings.
- Treat security findings as merge blockers and best-practice findings as guidance that hardens over time.
- Re-run only the layer you just fixed, then run the full validation once before merging.
When to Use
- Reviewing
azure-pipelines.ymlorazure-pipelines.yamlbefore merging a change. - Auditing a pipeline for hardcoded secrets,
:latestcontainer tags orcurl | bashpatterns. - Checking task version pinning,
displayName, caching and timeouts on an existing pipeline. - Adding a validation gate to an Azure Pipelines CI job.
When Not to Use
- Executing or testing a pipeline run: this skill does static analysis only.
- Looking up current task inputs or versions: use the live documentation sources listed below.
- Validating GitLab CI or GitHub Actions files: use the matching validator skill instead.
- Generating a new pipeline from scratch: use the Azure Pipelines generator skill instead.
Basic Usage
# Full validation (all layers)
bash 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
What ships with it
47 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/2026-10-02/Analysis.md 485 B
- .audits/2026-10-02/audit.json 548 B
- .audits/2026-10-02/Remediation.md 1.2 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/capability.txt 73 B
- evals/scenario-01/criteria.json 573 B
- evals/scenario-01/task.md 183 B
- evals/scenario-02/capability.txt 61 B
- evals/scenario-02/criteria.json 629 B
- evals/scenario-02/task.md 175 B
- evals/scenario-03/capability.txt 47 B
- evals/scenario-03/criteria.json 637 B
- evals/scenario-03/task.md 173 B
- evals/scenario-04/capability.txt 56 B
- evals/scenario-04/criteria.json 3.9 KB
- evals/scenario-04/task.md 622 B
- evals/scenario-05/capability.txt 67 B
- evals/scenario-05/criteria.json 2.8 KB
- evals/scenario-05/task.md 542 B
- evals/scenario-06/capability.txt 59 B
- evals/scenario-06/criteria.json 3.8 KB
- evals/scenario-06/task.md 660 B
- evals/scenario-07/capability.txt 45 B
- evals/scenario-07/criteria.json 3.2 KB
- evals/scenario-07/task.md 762 B
- evals/scenario-08/capability.txt 57 B
- evals/scenario-08/criteria.json 3.2 KB
- evals/scenario-08/task.md 664 B
- 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.
- 12d ago Changed 17fca339617e
- 16d ago Changed · +57 lines scan A → B bc2d20d31431
- 1mo 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 today), licensed MIT. It adds 135 tokens to every session and 2,840 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
google-cloud-slo-alert-configuration
Configures Cloud Monitoring PromQL-based Service Level Objective (SLO) alerting policies on Google Cloud for resources registered in App Hub or individually specified. Generates Terraform output. Use when the user asks to configure an SLO or Service Level Objective. Don't use for standard alerting policies.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
factory
Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or host automations.
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
factory-ship
Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.