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/abderrahimghazali/drupal-boost/deploymentnpx skills add abderrahimghazali/drupal-boost --skill deploymentgit clone --depth 1 https://github.com/abderrahimghazali/drupal-boostWhat 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.00052 | $0.01017 |
| Opus 5 | $0.00026 | $0.00508 |
| Sonnet 5 | $0.00010 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
deployment 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 2d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drupal Deployment
Deployment Order (Critical)
The correct order matters. Getting it wrong can break your site.
# 1. Enable maintenance mode (optional)
drush state:set system.maintenance_mode 1
# 2. Run database updates FIRST (needs old state to know what changed)
drush updatedb --no-cache-clear
# 3. Clear caches (rebuild container after code changes)
drush cache:rebuild
# 4. Import configuration
drush config:import -y
# 5. Clear caches again (config changes may alter the container)
drush cache:rebuild
# 6. Run deploy hooks (custom post-deploy logic)
drush deploy:hook
# 7. Disable maintenance mode
drush state:set system.maintenance_mode 0
Or use the drush deploy shortcut which runs the correct sequence.
GitHub Actions
# .github/workflows/drupal-ci.yml
name: Drupal CI
on:
push:
branches: [main, develop]
pull_request:
branches: [main]
jobs:
test:
runs-on: ubuntu-latest
services:
mysql:
image: mysql:8.0
env:
MYSQL_ROOT_PASSWORD: root
MYSQL_DATABASE: drupal
ports: ['3306:3306']
options: --health-cmd="mysqladmin ping" --health-interval=10s
steps:
- uses: actions/checkout@v4
- uses: shivammathur/setup-php@v2
with:
php-version: '8.3'
extensions: gd, pdo_mysql, mbstring
coverage: xdebug
- run: composer install --no-interaction --prefer-dist
- name: PHPCS
run: ./vendor/bin/phpcs --standard=Drupal,DrupalPractice web/modules/custom/
- name: PHPStan
run: ./vendor/bin/phpstan analyse web/modules/custom/ --level=6
- name: PHPUnit
run: ./vendor/bin/phpunit -c web/core web/modules/custom/
env:
SIMPLETEST_DB: mysql://root:[email protected]:3306/drupal
SIMPLETEST_BASE_URL: http://localhost:8080
GitLab CI
# .gitlab-ci.yml
include:
- project: 'drupalspoons/composer-plugin'
ref: '1.x'
file: '/templates/.gitlab-ci.yml'
variables:
_TARGET_PHP: "8.3"
_TARGET_DB: "mysql-8"
_PHPUNIT_EXTRA: "--group my_module"
DRUPAL_CORE: "11.x"
What ships with it
3 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.
- 2d ago First seen · 153 lines · 52 tokens per session scan A 4f097536c568
deployment is a skill published in the GitHub repository abderrahimghazali/drupal-boost (1 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 1,017 once invoked, about $0.0003 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
github-actions
Use this skill when authoring or debugging GitHub Actions workflows (.github/workflows/.yml) — e.g. "add CI for this Drupal project on GitHub", "run phpcs/phpstan/phpunit on pull requests", "cache composer dependencies", "deploy over SSH when main is pushed", "why didn't my workflow trigger", or anything involving…
gitlab-ci
Use this skill when authoring or debugging GitLab CI/CD pipelines (.gitlab-ci.yml) — e.g. "add a CI pipeline for this Drupal project", "run phpcs/phpstan/phpunit in GitLab CI", "deploy with drush from a pipeline", "why is my job not running", "cache composer dependencies", or anything involving stages, rules…
drupaltools-contrib-gitlab-ci
Generate and validate .gitlab-ci.yml files for Drupal modules using Drupal Association templates. Use this skill when you need to create GitLab CI configuration, update existing CI, or validate CI setup for a Drupal module.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
dsh-web-pre-push-checks
Use before pushing, opening or updating a pull request, or claiming dsh-web checks pass. Selects the required repository gates and diff-specific generation, build, and GUI evidence.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…