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 easingthemes/dx-aem-flow --skill auto-pipelinesgit clone --depth 1 https://github.com/easingthemes/dx-aem-flowWrote 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/easingthemes/dx-aem-flow/auto-pipelines)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/auto-pipelines"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/auto-pipelines.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 317 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00042 | $0.03945 |
| Opus 5 | $0.00021 | $0.01972 |
| Sonnet 5 | $0.00008 | $0.00789 |
| Haiku 4.5 | $0.00004 | $0.00394 |
Grade A, and why
auto-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 7d 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 — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You import ADO pipeline YAML files into Azure DevOps and set all required variables. Uses az pipelines (audit-wrapped) and reads config from .ai/automation/infra.json. Each project is self-contained — imports all enabled pipelines regardless of profile.
0. Prerequisites
source .ai/lib/audit.sh
export AUDIT_LOG_PREFIX=infra
Read .ai/automation/infra.json. Extract:
adoOrg— ADO org URLadoProject— ADO project namepipelineFolder— optional ADO pipeline folder path (e.g.\\KAI). If set, pipelines are created inside this folder.- Pipeline entries — only those without
"disabled": true
Read .ai/config.yaml to get scm.repo (repository name for pipeline import).
If automationProfile is consumer, pr-only, or pr-delegation (legacy): warn ⚠ Legacy profile — re-run /auto-init to migrate to per-project model. Proceed with all enabled pipelines.
Print: Importing <N> enabled pipelines
SimpleAgent + the KAI-HUB router are imported here like any other pipeline. SimpleAgent has no Lambda — its trigger is an Azure-native Service Hook + Incoming WebHook service connection (configured by /auto-webhooks, not here). But "no Lambda" only affects the trigger: the pipeline YAML still must be imported as an ADO definition and given variables, which is exactly this skill's job. So:
simple(ado-cli-simple.yml) — enabled by default when notdisabled.hub(ado-cli-hub.yml) — multi-repo only,"disabled": trueby default. Import only when explicitly enabled.
1. Import Pipelines
For each enabled pipeline (in order), import the YAML into ADO.
All pipelines use Claude Code CLI (single-step skill invocation): .ai/automation/pipelines/cli/ado-cli-<agent>.yml. The eval pipeline uses .ai/automation/pipelines/eval/ado-eval-pipeline.yml.
1a. Check if pipeline already exists
Before creating, check if a pipeline with this name already exists in the project:
EXISTING_ID=$(az pipelines list \
--name "<pipeline-name>" \
--project "<adoProject>" \
--organization "<adoOrg>" \
--query "[0].id" --output tsv 2>/dev/null)
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.
- 7d ago First seen · 357 lines · 42 tokens per session scan A fbf213956bc1
auto-pipelines is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 6d ago), licensed MIT. It adds 42 tokens to every session and 3,945 once invoked, about $0.0002 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
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.
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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.