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 meo-overviewgit 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/meo-overview)<a href="https://agentmods.dev/skills/acquia/acquia-skills/meo-overview"><img src="https://agentmods.dev/badge/skills/acquia/acquia-skills/meo-overview/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/meo-overview"><img src="https://agentmods.dev/badge/skills/acquia/acquia-skills/meo-overview.svg" alt="Reviewed on agentmods" width="80" 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 Data Exfiltration · line 73 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00041 | $0.01393 |
| Opus 5 | $0.00020 | $0.00696 |
| Sonnet 5 | $0.00008 | $0.00279 |
| Haiku 4.5 | $0.00004 | $0.00139 |
Grade A, and why
meo-overview 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MEO (Multi-site Enterprise Operations) Overview
Use when:
- Determining whether a subscription uses ACE or MEO
- Starting work on a MEO multi-site subscription
- Choosing between
acli api:*(ACE) andacli api:v3:*(MEO) commands - Discovering which MEO commands are available
ACE vs MEO — Choosing the Right Commands
Acquia Cloud Platform has two subscription types, each with its own API and CLI command prefix:
| ACE (Acquia Cloud Enterprise) | MEO (Multi-site Enterprise Operations) | |
|---|---|---|
| CLI prefix | acli api:* |
acli api:v3:* |
| API version | V2 (cloud.acquia.com/api) |
V3 (api.acquia.com/v3) |
| Model | One application → multiple environments, one Drupal site per environment | Subscription → Codebases + Environments → Sites → Site Instances (many Drupal sites per environment) |
| Use case | Single-site per environment | Multiple Drupal sites sharing an environment |
How to tell which type a subscription is: Look at the available commands. If acli api:v3:sites:list returns results, it is MEO. If acli api:applications:list is the primary entry point, it is ACE.
MEO Resource Model
Subscription
├── Codebases (shared git repos)
│ └── References (branches / tags)
└── Environments (runtime containers)
├── Site Instances (one per Site per Environment)
│ ├── Domains
│ └── Database + Backups
└── Deployments (code deploy operations)
Sites (logical Drupal sites, linked to a Codebase)
└── Site Instances (a Site deployed into an Environment)
Key relationships:
- A Codebase holds the shared git repository
- A Site is the logical definition of a Drupal site, referencing a Codebase
- An Environment is where code runs (prod, staging, dev, etc.)
- A Site Instance is a Site running inside an Environment (has its own database and domain)
Authentication
MEO uses the same Acquia Cloud credentials as ACE:
acli auth:login
acli auth:me
No separate login is needed. The api:v3:* commands automatically use the V3 API endpoint (https://api.acquia.com/v3).
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 · 161 lines · 41 tokens per session scan A f6b906cf7b49
meo-overview is a skill published in the GitHub repository acquia/acquia-skills (9 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 1,393 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-09-04.
Other skills, from other repositories
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…
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).