Azure/sap-automation-bootstrap is a customer-configuration and wrapper-pipeline repository for running the SAP Deployment Automation Framework through Azure DevOps. It stores deployment settings and invokes implementation templates from the separate sap-automation repository. Its catalogue skills and plugin help coding agents bootstrap Azure DevOps projects and explain the available wrapper pipelines.
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 Azure/sap-automation-bootstrap --skill sdaf-ado-pipeline-cataloguegit clone --depth 1 https://github.com/Azure/sap-automation-bootstrapWrote 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/azure/sap-automation-bootstrap/sdaf-ado-pipeline-catalogue)<a href="https://agentmods.dev/skills/azure/sap-automation-bootstrap/sdaf-ado-pipeline-catalogue"><img src="https://agentmods.dev/badge/skills/azure/sap-automation-bootstrap/sdaf-ado-pipeline-catalogue/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/azure/sap-automation-bootstrap/sdaf-ado-pipeline-catalogue"><img src="https://agentmods.dev/badge/skills/azure/sap-automation-bootstrap/sdaf-ado-pipeline-catalogue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00238 | $0.02239 |
| Opus 5 | $0.00119 | $0.01120 |
| Sonnet 5 | $0.00048 | $0.00448 |
| Haiku 4.5 | $0.00024 | $0.00224 |
Grade A, and why
sdaf-ado-pipeline-catalogue 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDAF — Azure DevOps pipeline catalogue
Context primer for the 13 pipeline wrappers shipped in
pipelines/. Answers "what does this pipeline do, what
inputs does it take, what does it read, and when should I use it?" using only
what docs/pipeline-reference.md and docs/07-00-operations.md document.
Two repository-resource files back the wrappers:
pipelines/resources.yml declares
sap-automation; pipelines/resources_including_samples.yml
declares sap-automation and sap-samples. Both currently use ref: main.
All pipeline files use trigger: none
(docs/pipeline-reference.md).
When to invoke
- "What does pipeline
03do?" / "when do I run10vs11vs12?" - "Which variable group does
05read?" / "what doesSDAF-Generalsupply?" - "What are the parameters for the workload-zone pipeline?"
- "How do I level up my ADO pipelines from upstream?"
- "Explain
20vs21vs22."
Do not invoke for:
- Creating the Azure DevOps project, agent pool, MSI, service connections, or
variable groups (
sdaf-ado-project-bootstrap). - Actually running a deployment — this skill primes context; it does not drive commands.
- GitHub Actions workflows.
Deployment wrappers
Each wrapper lives in
pipelines/ and extends a core template in
Azure/sap-automation. See
docs/pipeline-reference.md § Deployment wrappers.
| Wrapper | Purpose (documented) | Reads |
|---|---|---|
01-deploy-control-plane.yml |
Deploys control-plane resources and optional Web App. Key params: deployer, library, environment, use_deployer, reset, test. test is NOT forwarded to deployment scripts. reset may need multiple runs. |
SDAF-<control-plane> |
02-sap-workload-zone.yml |
Stores credentials in Key Vault and deploys the workload zone. test: true reaches the installer and exits after terraform plan. Params include inherit_settings. |
SDAF-<workload-environment> |
03-sap-system-deployment.yml |
Deploys SAP-system infrastructure from a prepared SYSTEM configuration. Params: sap_system, environment, test (plan-only via TEST_ONLY). |
SDAF-<workload-environment> |
04-sap-software-download.yml |
Downloads a selected combined BOM. Uses resources_including_samples.yml. Params: combined BOM, override, environment, region, extras, re_download. |
SDAF-<workload-environment> (+ shared values from SDAF-General) |
04-sap-software-download_v2.yml |
Documented alongside 04 in docs/pipeline-reference.md § Deployment wrappers: constructs a combined BOM from application, database, and kernel BOMs and derives region from environment. Uses resources_including_samples.yml. Public selection criteria versus 04 are unresolved in docs. |
SDAF-<workload-environment> (+ shared values from SDAF-General) |
05-DB-and-SAP-installation.yml |
Runs parameter validation and selected Ansible install stages. Params: system, environment, BOM, stage booleans, extras. The core job has no timeout. | SDAF-<workload-environment> |
07-sap-cal-installation.yml |
SAP CAL install wrapper. The referenced core template was absent from the validated core checkout; do not run until the selected core ref supplies a validated template (docs/pipeline-reference.md). |
SDAF-<workload-environment> |
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 · 148 lines · 238 tokens per session scan A 3191db462379
sdaf-ado-pipeline-catalogue is a skill published in the GitHub repository Azure/sap-automation-bootstrap (11 stars, last pushed 16d ago), licensed MIT. It adds 238 tokens to every session and 2,239 once invoked, about $0.0012 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
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.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.