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 Benknightdark/neo-skills --skill neo-azure-pipelinesgit clone --depth 1 https://github.com/Benknightdark/neo-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/benknightdark/neo-skills/neo-azure-pipelines)<a href="https://agentmods.dev/skills/benknightdark/neo-skills/neo-azure-pipelines"><img src="https://agentmods.dev/badge/skills/benknightdark/neo-skills/neo-azure-pipelines/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/benknightdark/neo-skills/neo-azure-pipelines"><img src="https://agentmods.dev/badge/skills/benknightdark/neo-skills/neo-azure-pipelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00066 | $0.01279 |
| Opus 5 | $0.00033 | $0.00639 |
| Sonnet 5 | $0.00013 | $0.00256 |
| Haiku 4.5 | $0.00007 | $0.00128 |
Grade A, and why
neo-azure-pipelines 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 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.
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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Pipeline Script Design Specifications
Perceive
- When version-specific syntax or task versions matter, verify them against
https://learn.microsoft.com/en-us/azure/devops/pipelines/?view=azure-devops; if browsing is unavailable, state the uncertainty and rely on bundled templates plus project evidence. - Identify the application's development language (e.g., .NET, Java, Python, Node.js) and its specific version requirements.
- Identify the target deployment platform (e.g., Azure App Service, Azure Kubernetes Service, Function App, or on-premises servers).
- Detect the project source code structure to confirm build tools (e.g., Maven, Gradle, Npm, NuGet) and testing frameworks.
- Read security and compliance requirements, including Static Application Security Testing (SAST), package vulnerability scanning, and container image scanning.
- Confirm environment variable requirements, secret information sources (e.g., Azure Key Vault), and Service Connection permissions.
- Proactively scan the
skills/neo-azure-pipelines/templates/directory to identify existing reusable template resources. Includes:- Build:
build/build-dotnet.yml - Deploy:
deploy/deploy-app-service.yml,deploy/deploy-iis.yml - Utils:
util/clean-artifact.yml,util/extract-artifact.yml,util/iis/*.yml, etc.
- Build:
Reason
- Compare documented task versions with existing configurations to determine if task versions need updating (e.g., using Checkout@v1 vs. Checkout@v4).
- Determine whether to adopt a multi-stage architecture based on project scale to achieve logical isolation of Build, Test, Staging, and Production.
- Evaluate and design build caching strategies, optimizing dependency package folders to reduce execution time.
- Design trigger mechanisms based on branching strategies, distinguishing trigger paths for Continuous Integration (CI) and Continuous Deployment (CD).
- Determine the applicability of deployment strategies, such as Blue-Green, Canary, or Rolling Update.
- Validate conditional execution syntax (Conditions) in Pipeline logic to ensure subsequent steps only execute on specific branches or after successful prerequisites.
- Prioritize using templates from
skills/neo-azure-pipelines/templates/to assemble the Pipeline, rather than writing raw YAML from scratch.- If the project is .NET and needs deployment to IIS, combine
build-dotnet.ymlanddeploy-iis.yml. - If artifact manipulation is required, prioritize using
util/extract-artifact.yml.
- If the project is .NET and needs deployment to IIS, combine
What ships with it
13 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.
- templates/build/build-dotnet.yml 3.3 KB
- templates/deploy/deploy-app-service.yml 2.6 KB
- templates/deploy/deploy-iis.yml 8.0 KB
- templates/util/clean-artifact.yml 1.5 KB
- templates/util/extract-artifact.yml 2.1 KB
- templates/util/iis/iis-backup.yml 3.2 KB
- templates/util/iis/iis-deploy-files.yml 4.6 KB
- templates/util/iis/iis-manage-website.yml 4.7 KB
- templates/util/iis/iis-rollback.yml 3.6 KB
- templates/util/iis/iis-start-website.yml 3.6 KB
- templates/util/iis/iis-stop-website.yml 3.4 KB
- templates/util/iis/iis-task.yml 5.6 KB
- templates/util/set-aspnetcore-env.yml 3.6 KB
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 First seen · 79 lines · 66 tokens per session scan A 47df5efbb391
neo-azure-pipelines is a skill published in the GitHub repository Benknightdark/neo-skills (7 stars, last pushed 6d ago), licensed MIT. It adds 66 tokens to every session and 1,279 once invoked, about $0.0003 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
insforge-cli
Use this skill whenever someone needs a backend, or a task touches InsForge backend or cloud infrastructure through the InsForge CLI: projects, SQL, migrations, RLS policies, functions, storage, backups, deployments, compute, secrets, config, schedules, logs, diagnostics, advisor scans and suppressions, import/export…
glab-runner-controller
A command-line tool for managing GitLab Runner controllers and their authentication tokens. A Runner controller coordinates the infrastructure used by GitLab Runners, which execute pipeline jobs.
deploy-ninja
Handles zero-downtime deployments: blue-green, canary releases, rolling updates, and feature flag rollouts. Covers Kubernetes, Docker, Cloudflare Workers, Terraform, and CI/CD pipeline setup. Use this skill when the user wants to deploy an application, set up a deployment pipeline, implement canary releases, configure…
cloud-build-basics
Teaches the fundamentals of Google Cloud Build (GCB). Covers core concepts, API enablement, console navigation to the Build History page, and the end-to-end workflow for creating and manually running a basic build trigger. Do not use for managing private pools or complex pipeline architectures.
offensive-container-escape
Container escape and breakout techniques targeting Docker, containerd, and Podman runtimes. Covers privileged container breakout via host filesystem mount and nsenter, Docker socket abuse through /var/run/docker.sock, Linux capability exploitation including CAPSYSADMIN, CAPSYSPTRACE, and CAPNETADMIN, cgroup v1…
offensive-cloud
Cloud security attack methodology covering AWS, Azure, and GCP. Includes credential harvesting (IMDS, /.aws, env vars, leaked CI secrets, instance roles), enumeration with cloud-specific tools (pacu, ScoutSuite, Prowler, ROADtools, gcpenum), privilege escalation paths (IAM PassRole, AssumeRole chains, Lambda/Functions…