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 acquia/acquia-skills --skill setup-external-ci-cdgit clone --depth 1 https://github.com/acquia/acquia-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/acquia/acquia-skills/setup-external-ci-cd)<a href="https://agentmods.dev/skills/acquia/acquia-skills/setup-external-ci-cd"><img src="https://agentmods.dev/badge/skills/acquia/acquia-skills/setup-external-ci-cd/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/setup-external-ci-cd"><img src="https://agentmods.dev/badge/skills/acquia/acquia-skills/setup-external-ci-cd.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.00016 | $0.03491 |
| Opus 5.5 | $0.00006 | $0.01396 |
| Sonnet 5.5 | $0.00003 | $0.00698 |
| Haiku 4.5 | $0.00002 | $0.00349 |
Grade D, and why
setup-external-ci-cd 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 28d 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.
mkdir -p ~/.ssh && echo "$ACQUIA_SSH_PRIVATE_KEY" > ~/.ssh/id_rsa && chmod 600 ~/.ssh/id_rsa 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.
mkdir -p ~/.ssh && echo "$ACQUIA_SSH_PRIVATE_KEY" > ~/.ssh/id_rsa && chmod 600 ~/.ssh/id_rsa Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `acli` (Acquia CLI) | `acli --version` | `curl -sSL https://github.com/acquia/cli/releases/latest/download/acli.phar -o /usr/local/bin/acli && chmod +x /usr/local/bin/acli` | How it starts
The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setting up external CI/CD for Cloud Platform (Drupal)
Connect your own CI/CD tool (GitHub Actions, GitLab CI/CD, or any Linux CI) to Acquia Cloud Platform:
your pipeline builds a deployable artifact, pushes it to the application's Acquia Git repository, and
Cloud Platform runs the Drupal deployment operations server-side. Every step has an acli command, so
the whole workflow is scriptable.
Use when:
- Wiring an existing GitHub/GitLab (or other) pipeline to build and deploy Drupal to Cloud Platform
- Migrating off Acquia Pipelines while keeping the same deploy-branch convention
- Scripting artifact build (
push:artifact) and environment deploys (code-switch) in CI
For the complete reference (full provider templates, appendices, and background), see the Acquia documentation.
Provider setup files — read the one matching the customer's CI tool:
- github-actions.md — GitHub Actions workflow files
- gitlab-ci.md — GitLab CI/CD
.gitlab-ci.yml
Related skills: ssh-key-management · environment-management · remote-access · scripting · codestudio (Acquia's built-in alternative).
Scope — ACE only, not MEO
Applies to Cloud Platform applications that have their own Acquia Git repository with dev/test/prod
environments. MEO codebases are not supported (different deployment model). Confirm before starting:
acli api:codebases:get-by-application <applicationUuid>
If the application resolves to a codebase, stop — this workflow does not apply.
How it works
Two mechanisms connect CI to Cloud Platform:
- SSH key — your runner authenticates to the Acquia Git remote with a registered key to push the artifact.
- Acquia CLI —
acli push:artifactbuilds a sanitized artifact (runscomposer install, commitsvendor/and scaffold files even when gitignored) and pushes it to a deploy branch + immutable tag;acli api:environments:code-switchpoints an environment at that ref, triggering the deploy and the server-sidepost-code-deployhook (updatedb,config:import,cache:rebuild).
What ships with it
2 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.
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.
- 28d ago First seen · 269 lines · 16 tokens per session scan D f3c128049618
setup-external-ci-cd is a skill published in the GitHub repository acquia/acquia-skills (10 stars, last pushed 7d ago), licensed MIT. It adds 16 tokens to every session and 3,491 once invoked, about $0.0001 per session on Opus 5.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-09-24.
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.
cloud-build-basics
Teaches the fundamentals of Cloud Build on Google Cloud. 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.
schedule-recipe
Turn 'run this every Friday at 4pm' into a working, copy-paste schedule on the user's actual runner. Use when asked to schedule a recurring AI task, set up a routine or cron job for a skill, automate a weekly report, or wire a skill into n8n or GitHub Actions. Produces the exact setup for the chosen runner plus the…
kotlin-tooling-gradle-to-kotlin-toolchain-project
Load when migrating or converting an entire Gradle Kotlin project (build.gradle(.kts), wrapper, libs.versions.toml, buildSrc) to the Kotlin Toolchain, including rewriting CI and replacing Gradle plugins that have no native Toolchain equivalent. Skip for porting one Gradle plugin or general Toolchain work once Gradle…