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 agentmods add skills/acquia/acquia-skills/pull-pushnpx skills add acquia/acquia-skills --skill pull-pushgit 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/pull-push)<a href="https://agentmods.dev/skills/acquia/acquia-skills/pull-push"><img src="https://agentmods.dev/badge/skills/acquia/acquia-skills/pull-push.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.01323 |
| Opus 5 | $0.00015 | $0.00661 |
| Sonnet 5 | $0.00006 | $0.00265 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
pull-push 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 yesterday.
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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull & Push with Acquia CLI
Platform: This skill applies to ACE (Acquia Cloud Enterprise) subscriptions only. For MEO (Multi-site Enterprise Operations), see MEO Site Instances for database and file operations.
Use when:
- Syncing your local environment with a Cloud Platform environment
- Pulling code, database, or files from Cloud to local
- Pushing code, database, files, or build artifacts to Cloud
Pull: Copy from Cloud to Local
Pull everything (code + database + files)
acli pull:all
Aliases: acli refresh, acli pull
Prompts you to select an environment, then copies code, database, and files to your local environment.
Options:
acli pull:all \
--dir=/path/to/project \
--no-code \ # skip code
--no-databases \ # skip database
--no-files \ # skip files
--no-scripts # skip post-pull scripts
Pull code only
acli pull:code
Pulls the latest code from the selected Cloud environment into your local directory.
acli pull:code --dir=/path/to/project
Pull database only
acli pull:database
Alias: acli pull:db
Imports a database backup from a Cloud environment into your local database.
Options:
acli pull:database \
--on-demand \ # force a fresh on-demand backup (not cached)
--no-import \ # download the backup file but don't import it
--multiple-dbs # download multiple databases (multisite)
Pull files only
acli pull:files
Copies Drupal public files (sites/default/files) from the Cloud environment to your local.
Run post-pull scripts manually
If you skipped scripts during a pull, run them separately:
acli pull:run-scripts
acli pull:run-scripts --dir=/path/to/project
Push: Copy from Local to Cloud
Push database
acli push:database
Alias: acli push:db
Uploads your local database to a Cloud Platform environment. Requires both a local and remote database to be configured.
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.
- yesterday Changed · +4 lines f0794c7b7133
- 5d ago First seen · 238 lines · 29 tokens per session scan A 6c7faab92b23
pull-push is a skill published in the GitHub repository acquia/acquia-skills (9 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 1,323 once invoked, about $0.0001 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
google-cloud-solution-guided-gke-ai-migration
Guides the migration of existing AI workloads (Cloud Run, Gemini API, Gemini Enterprise Agent Platform) to self-hosted GKE inference using gcloud and kubectl. Use when the user has an existing AI inference workload (on Cloud Run, the Gemini API, Gemini Enterprise Agent Platform, or a custom VM) and wants to move it to…
agent-platform-tuning
Agent Platform Model Tuning. Use when you need to fine-tune open models or Gemini models using Agent Platform infrastructure. Don't use for model training outside Agent Platform, model deployment to endpoints (use agent-platform-deploy), or managing serving endpoints (use agent-platform-endpoint-management).
gke-alert-configuration
Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using…
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
google-cloud-solution-n-tier-serverless-web-app
Assists in designing and implementing secure n-tier serverless web applications and microservices on Google Cloud. Use when users need architecture designs, security checklists, Terraform code, or deployment guidance for multi-tier serverless apps, regional data residency / European sovereignty compliance, zero-trust…
application-design-center-design-deploy
Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting…