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 codestudiogit 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/codestudio)<a href="https://agentmods.dev/skills/acquia/acquia-skills/codestudio"><img src="https://agentmods.dev/badge/skills/acquia/acquia-skills/codestudio.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Privilege Escalation · line 65 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00964 |
| Opus 5 | $0.00023 | $0.00482 |
| Sonnet 5 | $0.00009 | $0.00193 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
codestudio 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 4d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Studio with Acquia CLI
Platform: This skill applies to ACE (Acquia Cloud Enterprise) subscriptions only.
Use when:
- Setting up a new Code Studio project for a Cloud application
- Changing the PHP version used in Code Studio builds
- Migrating an existing
acquia-pipelines.ymlto a.gitlab-ci.ymlfile
Note: This skill covers Code Studio setup only. To trigger builds, check job status, or stream logs, use pipelines-cli (
pipelines-cli-pipeline-operations).
Code Studio is Acquia's GitLab-based CI/CD platform. It runs build pipelines, automated tests, and deployments for your Cloud Platform applications.
Set Up Code Studio (Wizard)
The wizard creates and configures a Code Studio project for your application:
acli codestudio:wizard
Alias: acli cs:wizard
The wizard will:
- Authenticate with your Cloud Platform application
- Connect to your GitLab instance
- Create or configure a Code Studio project
- Set up CI/CD variables
Non-interactive (provide all credentials upfront):
acli codestudio:wizard \
--key="$ACQUIA_KEY" \
--secret="$ACQUIA_SECRET" \
--gitlab-token="$GITLAB_TOKEN" \
--gitlab-project-id=12345 \
--gitlab-host-name=code.acquia.com
Security: Never pass credential values directly in the command line — they appear in shell history and process listings. Always source them from environment variables or a secrets manager.
Options:
| Option | Description |
|---|---|
--key |
Cloud Platform API key for Code Studio to use |
--secret |
Cloud Platform API secret for Code Studio to use |
--gitlab-token |
GitLab personal access token |
--gitlab-project-id |
Integer project ID of the GitLab project to configure |
--gitlab-host-name |
GitLab hostname (defaults to Acquia's instance) |
Change PHP Version in Code Studio
Update the PHP version used in Code Studio build containers:
acli codestudio:php-version <version>
Example:
acli codestudio:php-version 8.2
acli codestudio:php-version 8.3
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.
- 4d ago Changed · +3 lines 4dc6d7b9aa2e
- 8d ago First seen · 131 lines · 45 tokens per session scan A 60e15c2988b7
codestudio is a skill published in the GitHub repository acquia/acquia-skills (9 stars, last pushed 5d ago), licensed MIT. It adds 45 tokens to every session and 964 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
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…