Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/acquia/acquia-skillsnpx agentmods add skills/acquia/acquia-skills/pipeline-operationsWrote 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/acquia/acquia-skills/pipeline-operations)<a href="https://agentmods.dev/skills/acquia/acquia-skills/pipeline-operations"><img src="https://agentmods.dev/badge/skills/acquia/acquia-skills/pipeline-operations/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/acquia/acquia-skills/pipeline-operations"><img src="https://agentmods.dev/badge/skills/acquia/acquia-skills/pipeline-operations.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.00045 | $0.03305 |
| Opus 5 | $0.00023 | $0.01653 |
| Sonnet 5 | $0.00009 | $0.00661 |
| Haiku 4.5 | $0.00005 | $0.00331 |
Grade D, and why
pipeline-operations scanned grade D with 3 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 11d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo mv pipelines /usr/local/bin/pipelines Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
--source-key-path=~/.ssh/id_rsa \ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
wget https://cloud.acquia.com/pipelines-client/download -O pipelines How it starts
The opening of the file, as written. The whole thing — 583 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Operations with Acquia Pipelines CLI
Use when:
- Triggering a pipeline build
- Checking pipeline job status or streaming logs
- Terminating a running job
- Encrypting pipeline variables or connecting GitHub
Use the Pipelines CLI to trigger, monitor, and manage CI/CD pipeline jobs on Acquia Cloud.
See Getting Started for installation, authentication, and finding your application ID.
Starting a Pipeline Job
Important:
pipelines startfires immediately — there is no confirmation prompt. Verify your application ID and target branch before running.
Verify before starting
# Confirm the application ID
pipelines list-applications
# Check whether a job is already running on the branch
pipelines status --application-id=1g2i3b4b5o6u7s --job-id=latest
Proceed with start only after confirming the correct application and branch.
Start for the current branch
Run from inside your git repository:
pipelines start --application-id=1g2i3b4b5o6u7s
The CLI detects the current branch automatically.
Start for a specific branch
pipelines start \
--application-id=1g2i3b4b5o6u7s \
--vcs-path=feature/my-branch
Start and write artifact to a deploy branch
pipelines start \
--application-id=1g2i3b4b5o6u7s \
--vcs-path=feature/my-branch \
--deploy-vcs-path=deploy/my-branch
The build artifact is pushed to deploy/my-branch on success.
Start with environment variables
pipelines start \
--application-id=1g2i3b4b5o6u7s \
--vcs-path=main \
-D MY_VAR=foo \
-D ANOTHER_VAR=bar
Start and stream logs immediately
pipelines start --application-id=1g2i3b4b5o6u7s --tail
Start with log streaming delay
Useful when the build takes a moment to produce output:
pipelines start --application-id=1g2i3b4b5o6u7s --tail --delay=5
Start with retry options
Control how many times the log streaming retries on failure:
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.
- 11d ago First seen · 583 lines · 45 tokens per session scan D 4b8d9b9bcc02
pipeline-operations is a skill published in the GitHub repository acquia/acquia-skills (9 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 3,305 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, reaches for credential files, 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 PromQL-based Service Level Objective (SLO) alerting policies for Google Cloud 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.
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.
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.
comet-github-ci-triage
A workflow for diagnosing failed GitHub Actions checks on a Comet pull request. GitHub Actions runs automated builds and tests; a pull request is a proposed code change waiting to be reviewed and merged.
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…